AD/A320/179 Amdt 1 - Main Landing Gear - Axle Nut

The instrument hinges on three main legal-technical concepts set out in the source: applicability by manufacturer serial number, mandated inspection and corrective action in accordance with a manufacturer’s telex, and a reporting obligation to the manufacturer coupled with a specific compliance timetable.

Applicability. The AD is geographically and fleet-limited by Manufacturer Serial Number (MSN). It applies to Airbus A320 aircraft MSN 2275 to 2486 inclusive, but expressly excludes a discrete list of MSNs (2441, 2447, 2449, 2451, 2453, 2455, 2459, 2475, 2479 and 2484) (Applicability). This creates a precise eligibility boundary: only aircraft whose MSN falls within the inclusive range and is not one of the excepted MSNs are captured.

Mandated action per manufacturer telex. The substantive technical duty is to inspect and, if necessary, correct the MLG wheel axle nut locking hardware in accordance with Airbus AOT A320-32A1303 dated 4 July 2005 or later approved revisions (Requirement 1). The AD therefore grafts the content and method of compliance to a manufacturer-issued telex, and accepts later approved revisions of that telex as compliant. That design places the telex at the centre of the remedial standard.

Reporting. Requirement 2 imposes a reporting obligation to the aircraft manufacturer: operators must report the inspection results. The AD sets a short turnaround for that reporting, namely within seven days of the inspection (Compliance 2).

Compliance timing metric. The amendment changes the compliance metric from flight cycles to flight hours, with the inspection required within 500 flight hours from the effective date (Compliance 1 and Amendment note). The AD therefore ties regulatory timing to utilisation hours, not cycles, which affects how operators compute compliance windows.

Risk origin and purpose claim. The AD’s statement of background establishes the operational risk: a reported brake-dragging event, a separated axle nut, and an investigative finding that missing locking bolts, nuts, washers and cotter pins (not installed on the final assembly line) likely allowed the axle nut to loosen and separate. The AD’s stated purpose is to address this unsafe condition through inspection for the specified locking hardware (Background).

Interplay with foreign directives and replacement history. The AD references DGAC Emergency AD UF-2005-128 and an EASA reference number (2005-6092), indicating cross-recognition or common provenance of the identified unsafe condition. It also notes that UF-2005-128 replaces AD F-2005-120 (Note). The AD itself is labelled as an amendment (Amdt 1) to an original AD that first took effect on 12 July 2005 (Amendment note).

Delegation and issuing authority. The document bears the name of a CASA delegate, indicating the instrument is issued under CASA authority and executed via a delegate (signature block).

In sum, the main concepts are capture by MSN, mandatory manufacturer-based inspection and corrective action, short reporting obligations, a defined compliance window measured in flight hours, and formal linkage to both a manufacturer telex and related foreign airworthiness directives.

The AD explicitly targets operators of a subset of Airbus A320-series aeroplanes: those with Manufacturer Serial Numbers (MSN) between 2275 and 2486 inclusive, except for the specific MSNs excluded by the directive (Applicability). The source lists the excluded MSNs: 2441, 2447, 2449, 2451, 2453, 2455, 2459, 2475, 2479 and 2484. That delimitation is precise and excludes aircraft outside that serial number range and the expressly excepted serials.

Primary affected parties. Aircraft operators who possess or operate an affected MSN are the primary duty-bearers. They must implement the inspection and corrective action procedure specified in Airbus AOT A320-32A1303 (Requirement 1) and report the inspection results to Airbus (Requirement 2), all within the specified time limits (Compliance). The delegate of CASA signed the directive, so regulated entities are subject to CASA’s AD regime to the extent that regime applies, but the text itself specifies the operator duties rather than broader enforcement processes.

Maintenance organisations and engineers. Licensed maintenance providers who perform the inspection and any corrective actions will be operationally implicated. The AD dictates the method of inspection by reference to a specified Airbus telex; maintenance organisations must obtain that telex (AOT A320-32A1303 dated 4 July 2005 or later approved revisions) and implement its procedures. The telex is the technical standard the AD makes compulsory for the mandated action.

Aircraft manufacturers and their compliance records. Airbus is a recipient of the inspection reports (Requirement 2); the manufacturer therefore becomes a stakeholder in collating field data and may use those reports for further technical analysis or corrective action across the fleet. The AD thus imposes an information supply duty on operators that benefits the manufacturer’s safety monitoring.

Excluded and unaffected parties. Aircraft outside the specified MSN range, or one of the excluded MSNs, are not covered by this AD. The AD does not purport to reach other aircraft types, other components, or broader maintenance regimes beyond the specified inspection and reporting requirements.

Time-sensitive operational stakeholders. Because the AD sets a 500-flight-hour compliance window and a seven-day reporting deadline, scheduling stakeholders,flight operations planners, maintenance schedulers and commercial managers,are affected insofar as they must fit the mandated work into operational plans. The amendment switching the metric from flight cycles to flight hours will alter how utilisation is tracked for compliance, affecting operators’ calculations and scheduling decisions.

Regulatory counterparts. The AD references DGAC Emergency AD UF-2005-128 and an EASA reference, so foreign aviation authorities, their records and approval processes are relevant to how the AD aligns with international airworthiness action. The AD also notes that the DGAC Emergency AD replaces a prior AD (F-2005-120).

In short, the directive directly affects A320 operators of narrowly defined MSNs, their maintenance providers, and Airbus as the recipient of inspection reports; it tangentially affects operations and scheduling departments due to the time-limited compliance requirements.

The source sets out a compact set of mandatory duties for affected operators, and it attaches them to specific, short deadlines. The AD itself does not articulate affirmative rights or exemptions beyond the applicability exceptions and the “unless already accomplished” qualification.

Mandatory duties

• Inspect locking hardware. Operators must inspect the locking bolts, nuts, washers and cotter pins of each Main Landing Gear (MLG) wheel (Requirement 1). The method and corrective-actions standard are those set out in Airbus AOT A320-32A1303 dated 4 July 2005, or any later revision approved by the relevant authority. The AD thereby prescribes both the scope of the inspection and the technical standard that governs corrective measures.

• Apply corrective actions. Where inspection reveals missing or improperly installed locking hardware, operators must apply corrective actions in accordance with the Airbus AOT. The AD makes the AOT the compliance instrument, so the content of that AOT governs the remedial steps and acceptance criteria.

• Report results to Airbus. Operators must report the results of the inspection to the aircraft manufacturer (Requirement 2). The AD specifies a seven-day deadline for submitting that report following the inspection (Compliance 2).

• Meet the timing deadlines. Unless already accomplished, operators must complete the inspection within 500 flight hours from the effective date (Compliance 1). Reporting must occur within seven days of the inspection. The AD also clarifies that the amendment changes the compliance metric from flight cycles to flight hours (Amendment note).

Express qualifications and boundaries

• “Unless already accomplished.” The AD allows operators who have already completed the required inspection and corrective actions prior to the AD’s effective date to avoid repetition. The operator bears the onus of establishing that compliance was already accomplished.

• Applicability exceptions. Aircraft with MSNs expressly listed as excluded are outside the AD’s scope (Applicability). The duty to comply therefore depends on an operator’s aircraft MSN.

Rights and procedural points implicitly created by the AD

• Use of later approved revisions. The AD allows compliance with “later approved revisions” of Airbus AOT A320-32A1303. That qualification gives operators the right to rely on an updated AOT provided it is an approved revision; however, the AD does not define the approval process or who grants such approval within the text.

• Reporting as information flow to manufacturer. The AD establishes a duty to report to Airbus; that creates an information-right in the manufacturer to receive inspection data. The directive does not specify how Airbus will use or process that information, but it does create a statutory conduit for data to flow from operators to the manufacturer.

What the AD does not state as rights or duties

• No penalty clause. The AD does not itself specify sanctions, penalty amounts, or enforcement mechanisms. It imposes duties and timeframes, but does not articulate the legal consequences of non-compliance within the text provided.

• No extended compliance pathway or variance process. The AD does not set out a process for seeking variances, extensions, or alternate means of compliance in the text supplied; it confines compliance to the Airbus AOT and to the stated time limits.

In sum, the AD creates immediate, concrete maintenance and reporting duties for affected operators and maintenance organisations, with limited express qualifications (pre-accomplishment, applicability exclusions, allowance for later approved AOT revisions). It does not, in the text provided, articulate penalties, enforcement procedures, or administrative variance mechanisms.

The AD text supplied does not include express penalty provisions, fines, or an enforcement schedule. The instrument specifies mandatory actions and strict compliance windows,inspect within 500 flight hours and report within seven days,but it does not itself set out the legal sanctions for failure to comply or the administrative enforcement steps CASA might take for non-compliance.

What the AD does specify that relates to enforcement risk

• Compulsory actions with firm time limits. By setting a 500-flight-hour inspection deadline and a seven-day reporting deadline, the AD creates clear, time-sensitive obligations. Operationally, failure to meet those deadlines leaves the operator non-compliant with the stated requirements of this AD as of its effective date. The directive’s framing as an AD indicates it is a regulatory safety instrument issued under CASA authority (the signature block cites a delegate of the Civil Aviation Safety Authority), but the text does not reproduce the statutory enforcement provisions or penalties that CASA may have under its enabling legislation.

• No penalties in-text. There is no language within the supplied AD text that describes monetary penalties, administrative enforcement actions, or consequences such as grounding or restriction orders. There is likewise no description of an inspection, audit, or certification process to verify compliance, nor an appeal or variance mechanism within the instrument itself.

• Reporting obligation to Airbus. The AD requires operators to submit inspection results to the aircraft manufacturer within seven days. Although the AD does not specify follow-up enforcement steps by Airbus, the reporting requirement creates an information flow that could be relevant to later investigations or compliance assessments.

Implications for operators

• Compliance risk remains operational. Although penalties are not set out in the text, operators face practical risk: the AD makes the inspection and reporting duties mandatory for covered MSNs, and non-compliance would leave an operator unable to point to the AD-prescribed remedy for the identified unsafe condition.

• Enforcement likely lies outside the AD text. The absence of penalties in the text means that any enforcement, certification consequences, or sanctions would rely on the wider legal framework under which CASA operates or on agency administrative processes that are not reproduced here. The AD’s signature by a CASA delegate indicates the instrument forms part of CASA’s regulatory output; the application of enforcement tools would depend on CASA’s authoritative powers and procedures not contained in this document.

To summarise, the AD creates firm duties and deadlines but does not itself state penalties. Operators must treat the obligations as mandatory and time-critical; the AD’s text does not set out the means by which non-compliance will be sanctioned, so enforcement consequences fall beyond the instrument’s express content in the material provided.

The AD explicitly references related airworthiness directives from other authorities and ties compliance to a manufacturer-issued telex. Those links indicate cross-jurisdictional alignment and the role of manufacturer technical material within regulatory compliance, but the AD does not reproduce or restate enabling legislation, enforcement provisions, or administrative rules beyond its immediate content.

Cross-reference to foreign directives and EASA. The AD’s Note refers to DGAC Emergency Airworthiness Directive No. UF-2005-128 and states that it is approved under EASA reference no. 2005-6092 dated 13 July 2005. The AD further notes that DGAC AD UF-2005-128 replaces AD F-2005-120 (Note). That cross-reference shows the AD is connected to parallel airworthiness actions taken by France’s Directorate General for Civil Aviation (DGAC) and an EASA reference number, which suggests harmonisation of safety responses across jurisdictions for the same unsafe condition. The AD therefore interacts with those foreign directives insofar as they address the same technical problem, and it recognises the replacement history among those instruments.

Manufacturer technical material as compliance standard. The AD requires operators to inspect and to apply corrective actions in accordance with Airbus AOT A320-32A1303 dated 4 July 2005 or later approved revisions (Requirement 1). This design integrates manufacturer-issued telexes into regulatory compliance, making the AOT effectively a delegated technical standard. The effect is that compliance with the AD necessarily involves following manufacturer material, and any changes to that material that are “approved revisions” are acceptable under the AD, implying an approval process outside the AD. Thus, the AD interacts with the manufacturer’s own technical documentation and with whatever regulatory approval process exists for revisions.

Amendment interplay. The AD is an amendment (Amdt 1) that changes the compliance metric from flight cycles to flight hours while retaining the technical content. This indicates an internal interaction within the body of airworthiness directives: the amendment updates an earlier AD (original issue effective 12 July 2005) without changing substantive remedial steps. The AD therefore forms part of an iterative regulatory response to the identified problem.

Omitted legal procedural detail. The AD does not state or reproduce the enabling statutes, CASA’s enforcement powers, or administrative processes such as how operators might seek an alternative method of compliance or an extension. It does not specify whether compliance with the AD substitutes for other regulatory obligations or whether operators must separately notify CASA upon completion. Those procedural interactions with other legal instruments and agency processes are not contained in this text.

Information flows to the manufacturer. The reporting requirement,results must be sent to Airbus within seven days,creates a compliance-related information flow external to the regulator-manufacturer-authority triangle. The AD does not specify whether the manufacturer will notify CASA or other authorities, but the mandated reporting establishes an interaction between operator duties and manufacturer information-gathering, which can feed into further regulatory or manufacturer-initiated actions.

In short, the AD aligns with related foreign directives (DGAC and EASA references) and makes manufacturer technical material the operative compliance standard. It does not, in the text provided, set out the broader legal regime’s enforcement mechanisms, variance processes, or the administrative approvals that qualify later AOT revisions.

The AD is presented as Amendment 1 (Amdt 1) to an original Airworthiness Directive for Airbus A320 main landing gear axle nut locking hardware. The material supplied contains a concise amendment history embedded in the instrument.

Original issue. The source states that the original issue of this Airworthiness Directive became effective on 12 July 2005 (Amendment note). The current document is an amendment to that original AD.

Current amendment (Amdt 1). The current amendment (labelled AD/A320/179 Amdt 1) becomes effective on 15 July 2005 (effective date). The single substantive change effected by this amendment is the substitution of the compliance metric: the compliance time was changed from flight cycles to flight hours. The AD explicitly says the amendment changes compliance time from flight cycles to flight hours but "retains rest of the technical content of the original issue" (Amendment note). No other technical changes are recorded in the supplied text.

Relationship to DGAC/EASA ADs. The AD’s Note states that DGAC Emergency AD No. UF-2005-128, as approved under EASA reference no. 2005-6092 dated 13 July 2005, refers. The note further states that AD UF-2005-128 replaces AD F-2005-120 which is cancelled (Note). That shows a contemporaneous sequence of airworthiness directives across jurisdictions, with UF-2005-128 taking the place of earlier F-2005-120; the CASA AD recognises these foreign actions.

No further amendments recorded in the supplied text. The AD allows compliance with Airbus AOT A320-32A1303 dated 4 July 2005 or later approved revisions, signalling that subsequent approved revisions of the AOT may exist and be accepted for compliance; however, the AD record here does not list any later AOT revisions or subsequent AD amendments beyond Amdt 1.

Signature and date. The AD is signed by James Coyne, Delegate of the Civil Aviation Safety Authority, on 14 July 2005, which situates the amendment’s administrative finalisation immediately prior to its effective date (14 July signature, 15 July effective).

To summarise the amendment history as set out in the document: original AD effective 12 July 2005; Amendment 1 becomes effective 15 July 2005 and changes the compliance metric from flight cycles to flight hours while leaving the technical instructions unchanged; contemporaneous DGAC/EASA AD activity is acknowledged, with a noting that one foreign AD has replaced a prior one.

The supplied AD text contains no litigation history, references to court decisions, appeals, or judicial review related to this instrument. There are no cases named in the document, and the text does not recount any tribunal or court outcomes arising from the AD or its enforcement. The AD is an administrative safety directive signed by a CASA delegate; the document records the safety rationale, technical requirements and compliance deadlines, but it includes no information about any litigation or contested administrative proceedings.

Where litigation or disputes might arise is not stated in the AD. The AD does not set out any process for seeking a review, appeal, or an alternate means of compliance within its own text. The lack of litigation history in the document means that, based solely on the supplied material, there are no reported court or tribunal decisions to cite that interpret, modify or stay the AD.

Users requiring information on litigation, judicial review or contested enforcement of this AD would need to consult external administrative law records, CASA enforcement records, or judicial databases. That material is not reproduced here and therefore cannot be asserted or summarised from the supplied text.

The AD is short, but several practical and legal pitfalls for operators flow directly from the instrument’s precise language. The following are concrete points drawn from the text that commonly trip up compliance if overlooked.

Applicability is strictly by MSN range with discrete exclusions. The AD applies only to Airbus A320 aircraft with MSNs 2275 to 2486 inclusive, but lists ten specific MSNs that are excluded. Operators must verify the MSN for each airframe precisely. Assuming applicability by model alone, rather than by MSN and the specified exclusions, risks unnecessary work or missing an aircraft that is in scope (Applicability).

“Unless already accomplished” requires documentary proof. The Compliance paragraph allows operators who have already completed the inspection prior to the AD’s effective date to avoid repeating it. However, the AD itself does not set out what evidence suffices to establish pre-accomplishment. Operators should ensure contemporaneous records document the inspection and any corrective actions, because the AD’s text presumes the operator can demonstrate prior compliance (Compliance 1).

Timing metric change affects scheduling. The amendment converts the compliance metric from flight cycles to flight hours and requires completion within 500 flight hours from the effective date. Operators who previously planned maintenance around cycles must re-calculate based on flight hours. Miscomputing utilisation can produce missed deadlines. The AD explicitly notes this change in compliance metric (Amendment note; Compliance 1).

Mandatory reliance on a specific AOT and its approved revisions. The AD requires inspection and corrective action “in accordance with Airbus AOT A320-32A1303 dated 4 July 2005 or later approved revisions” (Requirement 1). Operators must obtain that exact telex and ensure that any later revision relied upon is an approved revision. Using an unapproved or unofficial telex, or deviating from the telex without an approved alternative method of compliance, would not comply with the AD as written.

Short reporting window. The AD requires reporting results to the manufacturer within seven days of the inspection (Compliance 2). This is a short turnaround for compiling and transmitting inspection results; operational teams should allow for administrative time to assemble the report and transmit it to Airbus within the deadline.

No in-text enforcement or variance process. The AD does not set out how to seek an alternative method of compliance, an extension, or other administrative relief. Operators should not assume that variances are accommodated; any request for an alternative compliance pathway or extension would need to be pursued under the broader regulatory framework or by contacting CASA, noting the AD itself contains no process.

Interplay with foreign ADs and replacement history. The Note cross-references DGAC Emergency AD UF-2005-128 and states it replaces AD F-2005-120 (Note). Operators with international fleets should check whether equivalent directives in other jurisdictions impose different reporting routes or additional requirements. The AD’s reference to those documents suggests alignment but does not itself harmonise procedural differences across jurisdictions.

Risk of missing the effective date. The amendment was signed 14 July 2005 and became effective 15 July 2005. The original AD was effective 12 July 2005. Operators must be alert to rapid issuance and short lead times for safety directives.

In short, common gotchas include misidentifying applicability, failing to produce documentary proof of prior compliance, miscalculating the flight-hours compliance window, relying on non-approved telex revisions, missing the short seven-day reporting deadline, and assuming the AD contains enforcement or variance procedures when it does not.

The AD prescribes a clear, short sequence of actions. Below is an operational checklist grounded in the AD’s text; it follows the order required by the directive and notes documentary and scheduling considerations implicit in the AD.

1. Determine applicability by MSN.

   • Confirm the aircraft’s Manufacturer Serial Number (MSN).
   • The AD applies only to A320 aircraft MSN 2275 to 2486 inclusive, excluding MSNs 2441, 2447, 2449, 2451, 2453, 2455, 2459, 2475, 2479 and 2484 (Applicability).
   • If the aircraft’s MSN is outside that range or is one of the excluded MSNs, the AD’s mandatory requirements do not apply.

2. Establish whether the inspection has “already [been] accomplished”.

   • If an inspection complying with Airbus AOT A320-32A1303 (or a later approved revision) was completed prior to the effective date, compile records that demonstrate the date, scope and outcome of that inspection.
   • The AD’s compliance clause recognises prior accomplishment; ensure documentation is robust to substantiate that fact (Compliance 1).

3. Obtain the Airbus AOT A320-32A1303 dated 4 July 2005 (or any later approved revision).

   • The AD requires inspection and corrective action “in accordance with Airbus AOT A320-32A1303 dated 4 July 2005 or later approved revisions” (Requirement 1).
   • Do not rely on informal guidance; obtain the official telex and confirm whether any later approved revisions exist and are applicable.

4. Plan and perform the inspection within the mandated window.

   • Unless already accomplished, perform the inspection within 500 flight hours from the AD’s effective date (Compliance 1).
   • The AD specifies inspection of the locking bolts, nuts, washers and pins (cotter pins) of each MLG wheel. Execute the inspection scope and acceptance criteria as set out in the AOT.

5. Apply corrective actions where required.

   • If the inspection reveals missing, loose or improperly installed locking bolts, nuts, washers or pins, apply corrective actions as specified in the Airbus AOT. The AD makes those corrective actions the required remediation (Requirement 1).

6. Report inspection results to Airbus within seven days.

   • After completing the inspection, submit the results to the aircraft manufacturer within seven days of the inspection date (Compliance 2; Requirement 2).
   • Ensure the report contains the details mandated by the AOT or by Airbus reporting templates if specified. The AD does not set out the report format; follow manufacturer guidance.

7. Retain records.

   • Keep contemporaneous maintenance records that document the inspection, any corrective action, the completion date, and the report submission to Airbus. These records support the “unless already accomplished” qualification for other aircraft and will be necessary to demonstrate compliance if questioned.

8. Coordinate maintenance scheduling to fit the 500-flight-hour deadline.

   • Because the AD measures the compliance window in flight hours (Amendment note), verify flight-hour counters and ensure the inspection is scheduled before the 500-flight-hour threshold. Adjust flight planning if necessary to secure maintenance time without exceeding the limit.

9. Confirm any later-approved AOT revisions and approvals.

   • If relying on a later revision of the AOT, confirm that the revision is an “approved revision” as allowed by the AD. If in doubt, seek confirmation from the authority or Airbus.

10. Communicate with stakeholders.

    • Notify operations, maintenance control, and airworthiness management of the AD, the aircrafts affected, the deadlines, and the reporting obligation.
    • Ensure that the maintenance organisation performing the work is authorised to carry out the tasks per the AOT.

11. Track cross-jurisdictional obligations.

    • Note the AD references DGAC Emergency AD UF-2005-128 (as approved under EASA reference no. 2005-6092) and indicates UF-2005-128 replaces AD F-2005-120 (Note). If the aircraft operate internationally, verify whether parallel directives or local implementation steps are required in other jurisdictions and whether reporting obligations differ.

12. Seek guidance if needed.

    • The AD does not set out variance or alternative compliance procedures. If an operator believes an alternate method of compliance is necessary, or if any ambiguity exists regarding what constitutes an approved AOT revision, the operator should contact the regulator or Airbus for clarification prior to deviating from the AD’s requirements.

This sequence tracks the AD’s express requirements: identify applicability; perform the AOT-prescribed inspection within 500 flight hours unless already done; apply corrective actions per the AOT; report results to Airbus within seven days; and retain documentation to substantiate compliance.