AD/BAe 146/122 - Nose Landing Gear Axle Spacer

The AD is built around a small set of technical and regulatory concepts drawn from the directive text. Those concepts determine who must act, what act must be done, and how compliance is to be evidenced.

• Applicability: The AD applies to a clearly defined fleet: “All Models BAe 146 and AVRO 146‑RJ series aeroplanes” (Applicability). This means every airframe within those model lines is captured by the directive’s requirement.

• Mandatory modification versus inspection: The AD’s operative wording is replacement. It states that it “requires the replacement of the existing nose wheel abutment rings with revised nose wheel abutment rings” (Background; Requirement). The directive therefore imposes a positive modification duty rather than a one‑off inspection or an operational limitation.

• Normative technical material: Compliance must be achieved “per SB 32‑174‑70676A Initial issue or later EASA approved revision” (Requirement). The service bulletin is the technical specification for the work. The AD also expressly references “EASA AD 2006‑0137 dated 23 May 2006” (Requirement note), linking the CASA AD to the corresponding EASA action and to the potential for later EASA‑approved revisions to the service document.

• Failure mode and hazard addressed: The background describes the mechanical failure mode in detail. Key terms used are “abutment ring,” “internal chamfer,” “wheel clamping loads,” “machined radius at the root of the stub axle,” “wheel nut locking bolts,” and “nose wheel retaining nut” (Background). The hazard pathway is: incorrect orientation of the abutment ring → ring displaced outboard → locking bolts not fully engaged → wheel nut can loosen under normal loads → wheel assembly detaches; secondary hazard: clamping loads on stub axle radius may cause damage. The revised ring’s design intent is defensive: if fitted incorrectly it will prevent the retaining nut from engaging with axle threads, thereby preventing an incorrectly installed ring from leaving the wheel retaining nut improperly engaged (Background).

• Timing: The AD imposes a finite compliance window: effective 3 August 2006, with replacement required “Prior to 31 May 2007” (Compliance; Effective date). The gap between effective date and compliance date creates a scheduling window for operators and maintenance organisations.

• Regulator and authorisation: The AD is promulgated by the Civil Aviation Safety Authority’s delegate,James Coyne,who signed on 20 June 2006 (Signature and date). The AD functions as the CASA instrument imposing the modification requirement.

These concepts determine the legal and practical contours of the intervention: a fleet‑wide, mandatory, component replacement action to be executed to a specified service bulletin and timed before a calendar deadline, with an explicit cross‑reference to a corresponding EASA AD.

The AD’s text identifies a narrow set of directly affected parties and implies others by the nature of the requirement.

Directly affected parties:

• Aircraft owners and operators of “All Models BAe 146 and AVRO 146‑RJ series aeroplanes” (Applicability). These entities are subject to the mandatory replacement requirement and must ensure the work is completed by the compliance date.
• Maintenance organisations, engineers and MROs that perform the modification specified in “SB 32‑174‑70676A Initial issue or later EASA approved revision” (Requirement). The service bulletin is the technical instrument through which the work must be carried out; maintenance providers supply labour, parts fitting, and paperwork.
• Parts suppliers/manufacturers responsible for supplying the “revised nose wheel abutment rings” required by the AD (Background; Requirement). They must produce parts that meet the design intent described in the AD and approved in the referenced service documentation or EASA revision.

Indirectly affected parties:

• Flight operations and scheduling departments within operator organisations, because each aircraft will require out‑of‑service time to have the replacement performed within the compliance window (Compliance).
• Continuing airworthiness managers and delegated persons who record compliance and update maintenance records to reflect the replacement action.
• Regulators and oversight bodies, who are responsible for verifying compliance with the AD in their surveillance and audit activities. The AD itself is issued by CASA (Delegate James Coyne); it also “refers” to EASA AD 2006‑0137, so European regulatory action is linked to the directive (Requirement note).

Who pays:

• The AD requires a physical part replacement; the cost of parts, labour, ferry or grounding time, logistics and any consequential inspections or repairs will fall to the operator or the aircraft owner. The directive does not allocate funding or compensation; it imposes the technical requirement. Because the AD mandates replacement “per SB 32‑174‑70676A” and the SB sets the work scope, operators will pay for acquisition of “revised nose wheel abutment rings” and for the installation work (Requirement; Background).

Who decides:

• The CASA delegate, as represented by the signature block “James Coyne, Delegate of the Civil Aviation Safety Authority” (Signature and date), is the issuing authority. The AD’s allowance for “later EASA approved revision” of the service bulletin creates a limited decision node: operators may use later EASA‑approved revisions rather than the initial issue of SB 32‑174‑70676A (Requirement). The AD does not contain provisions for alternative methods of compliance; any alternative would likely require regulatory acceptance, but that is not addressed in the text.

Who documents and certifies compliance:

• The text does not describe the certification paperwork process; by implication the maintenance organisation or delegated person who performs the SB work will produce the maintenance release and update the aircraft’s maintenance records showing compliance with the AD (Requirement; Compliance). The AD itself, however, does not include documentation templates or explicit record requirements.

In sum, the direct economic and operational burden lands on BAe 146 and AVRO 146‑RJ operators and their maintenance suppliers, with regulators providing the mandatory framework and cross‑reference to EASA material.

The AD imposes a discrete set of duties and creates a limited set of choices for affected parties. The AD text is terse; the legal obligations are the stated mandatory actions, and the limited operational discretion arises from the AD’s reference to acceptable technical material.

Primary duties:

• Replace existing nose wheel abutment rings with revised rings: The AD “requires the replacement of the existing nose wheel abutment rings with revised nose wheel abutment rings” (Background; Requirement). This is the central legal duty created by the instrument.
• Perform the replacement in accordance with specific technical material: Work must be done “per SB 32‑174‑70676A Initial issue or later EASA approved revision” (Requirement). That limits permissible methods to the service bulletin’s procedures or later EASA‑approved revisions.
• Complete the replacement within the time‑window: The AD specifies completion “Prior to 31 May 2007” and notes the AD “becomes effective on 3 August 2006” (Compliance; Effective date). Operators must schedule and execute the work inside that window.

Permissible choices and limited rights in the text:

• Choice of service bulletin revision: The AD allows use of the initial SB or a “later EASA approved revision” (Requirement). That gives operators a narrow right to use a later, EASA‑approved iteration of the SB if one exists at the time of compliance.
• Use of EASA AD cross‑reference: The AD “Note: EASA AD 2006‑0137 dated 23 May 2006 refers” (Requirement note). That cross‑reference signals that operators should consult the EASA AD for context and potentially for alternative or additional instructions, but the CASA AD itself governs Australian continuing airworthiness.

What the AD does not grant or specify (limits to rights and duties):

• No alternative method of compliance is provided in the AD text. The AD prescribes a single compliance approach (replacement per SB), and does not set out any approved alternative means of compliance or delegated acceptance procedure. If an operator wishes to use an alternative method, the AD text does not state a process for approval.
• No inspection‑only option: The AD’s wording requires replacement; it does not provide for merely inspecting or re‑orienting existing rings. The directive explicitly states the purpose of the revised part design: to ensure that an incorrectly fitted abutment ring will prevent the retaining nut from engaging, thereby preventing a dangerous installation from remaining functional (Background).
• No penalties or enforcement process specified: The AD does not contain text setting out penalties for non‑compliance, nor does it set out the enforcement mechanisms or surveillance procedures; it simply issues the requirement and dates (Effective date; Compliance).

Operational obligations implied by the duty to replace:

• Operators will need to obtain the revised part and follow the SB’s procedural steps. The SB is the performance standard the AD references for technical compliance (Requirement).
• Maintenance releases and continuing airworthiness records should record the AD compliance, although the AD text does not specify record‑keeping procedures or format.

In short, the AD imposes a narrow, mandatory duty to replace a specific component across an entire model line, prescribes one compliant technical route (the designated SB or later EASA‑approved revision), and fixes a completion deadline, while leaving administrative, documentation, and enforcement details to the broader regulatory regime or to operational practice rather than to the AD text itself.

The AD text itself supplies no penalty schedule, enforcement clauses or explicit inspection and sanction procedures. The document records the mandatory technical action, the effective date “3 August 2006” and the compliance deadline “Prior to 31 May 2007” (Compliance; Effective date), but does not include provisions that describe how non‑compliance will be policed or penalised.

What the AD does provide that is relevant to enforcement and regulatory action:

• A clear technical obligation and timeline: By prescribing replacement “per SB 32‑174‑70676A Initial issue or later EASA approved revision” and setting a firm compliance date, the AD creates an objective standard against which regulatory audit or surveillance can measure an operator’s compliance (Requirement; Compliance).
• A signatory authority: The AD is issued under the authority of CASA, as shown by the signature block “James Coyne, Delegate of the Civil Aviation Safety Authority” (Signature and date). That signature identifies the issuing authority; practical enforcement would flow from CASA’s statutory powers, although those are not described in the AD text.

Missing from the text (and therefore not to be assumed):

• The AD does not list fines, suspension powers, or other sanctions in the document itself. It does not specify the inspection regime to be used by CASA or the procedural steps for CASA to validate compliance.
• The AD does not describe the consequences for continuing to operate an aeroplane that has not had the replacement performed by the compliance date. The AD sets the requirement, which typically becomes part of the airworthiness obligations for the aircraft, but the AD text does not lay out the administrative or enforcement steps.

Practical inference (within the text’s limits):

• Because the AD creates a compulsory modification requirement and fixes a compliance deadline, an operator that fails to complete the work could be subject to regulatory action by the Civil Aviation Safety Authority under its broader statutory powers. The AD itself does not articulate those powers or the specific remedies or penalties.

For an operator or maintenance organisation planning compliance or advising clients, the absence of specified penalties in the AD means that the immediate focus should be ensuring technical compliance within the stated timeframe and properly recording the work, because those are the observable metrics that regulatory surveillance teams will check. The AD’s cross‑references to EASA material may also be relevant in international oversight or when coordinating parts and procedures with foreign certificating authorities, but the AD text contains no enforcement matrix.

The AD explicitly creates cross‑references to other regulatory instruments and prescribes technical materials that have legal relevance for compliance. The interaction points are confined to what the AD text states.

Express cross‑references in the AD:

• EASA AD: The AD contains a note: “Note: EASA AD 2006‑0137 dated 23 May 2006 refers” (Requirement note). That indicates the CASA AD is aligned with or follows an EASA action. Where EASA has issued an AD for the same problem, the EASA AD may contain similar or complementary requirements, and the CASA AD explicitly points operators to that source for reference.
• Service Bulletin as the technical standard: The AD mandates modification “per SB 32‑174‑70676A Initial issue or later EASA approved revision” (Requirement). Service bulletins are the technical documents that describe the procedure and parts; by tying compliance to an SB or its later EASA‑approved revisions, the AD makes the SB normative for the purposes of meeting the AD.

Consequences of those interactions:

• Regulatory harmonisation: The AD’s reference to EASA AD 2006‑0137 and acceptance of an EASA‑approved revision of the SB creates an interoperability bridge between CASA’s directive and EASA’s oversight regime. An operator using an EASA‑approved revision of the SB is explicitly permitted by the AD, which reduces the risk of conflicting technical directions between jurisdictions.
• Technical conformity obligation: Because compliance is to be performed “per SB 32‑174‑70676A … or later EASA approved revision,” an operator’s compliance will be measured against the procedures and parts specified in that SB and any later EASA‑approved revision. That situates the AD within a framework where technical documentation approved by EASA plays a role in satisfying CASA’s requirement.

What the AD does not state about interaction:

• The AD does not cite, interpret, or modify other Australian legislative instruments, regulations or CASA manuals. It does not set out how operators should record compliance in national continuing airworthiness records, nor does it describe whether compliance with the AD alters other regulatory obligations. Those matters are implied to be part of normal continuing airworthiness obligations rather than being set out in the AD.
• The AD does not specify how an alternative means of compliance might be approved by CASA or whether acceptance of EASA materials is automatic in all circumstances. It allows the use of later EASA‑approved SB revisions, but it does not set out a general approval route for other alternatives.

Practical implications for operators working cross‑jurisdictionally:

• If an operator is subject to both CASA and EASA jurisdiction (for example, an operator that also maintains certification obligations in Europe), the AD’s explicit reference to EASA AD 2006‑0137 and allowance for EASA‑approved SB revisions can simplify compliance planning because it creates a direct point of alignment.
• Because the AD makes the SB normative, operators sourcing parts or technical support internationally should ensure the parts conform to the SB’s specification and any EASA‑approved revisions referenced in the AD.

In summary, the AD interacts with external technical and regulatory instruments by: (1) making a particular service bulletin the normative method of compliance, and (2) explicitly referring to an EASA AD, thereby aligning the CASA requirement with EASA action. The AD does not, within its text, attempt to address broader statutory enforcement mechanisms or record‑keeping modalities; those are left to the wider regulatory framework outside the AD.

The AD text provides a compact amendment and issue chronology. There is no multi‑stage amendment record within the document itself; rather it records the following temporal milestones and cross‑references:

• EASA AD reference date: The document notes “EASA AD 2006‑0137 dated 23 May 2006 refers” (Requirement note). This indicates that an EASA airworthiness directive dealing with the same subject matter was issued on 23 May 2006. The CASA AD acknowledges that EASA action as relevant.

• CASA signature and issue date: The AD is signed by “James Coyne, Delegate of the Civil Aviation Safety Authority” and dated “20 June 2006” (Signature and date). That is the CASA issuing date captured on the instrument.

• CASA effective date: The AD states, “This Airworthiness Directive becomes effective on 3 August 2006” (Compliance; Effective date). That is the date from which the AD’s effect is to be treated as in force for the purposes of compliance.

• Compliance deadline: The AD requires operators to modify the nose landing gear “Prior to 31 May 2007” (Compliance). That fixes the window between the AD becoming effective and the date by which the mandated replacement must be completed.

• Service Bulletin reference and allowance for later revisions: The AD mandates the replacement “per SB 32‑174‑70676A Initial issue or later EASA approved revision” (Requirement). This particular phrase creates a standing permission to use later EASA‑approved revisions of the specified SB should they be issued. The AD itself contains the initial instruction and does not list any subsequent CASA amendments, but it expressly permits reliance on EASA‑approved revisions to the SB.

What the AD does not contain, and therefore has no amendment record for:

• The AD does not list any subsequent amendments to the CASA AD text. The document as provided shows only the original issue and its dates; it does not record any later CASA amendments or superseding ADs.
• The AD does not provide an annexed revision log within the document. The only revision pathway it contemplates is the use of later EASA‑approved revisions of the service bulletin.

Operators and maintainers consulting this AD should therefore treat the document as a single‑issue CASA AD with: (a) an issuing date (20 June 2006), (b) an effective date (3 August 2006), (c) a compliance deadline (31 May 2007), and (d) a standing permission to use later EASA‑approved SB revisions. Any later amendments to the CASA AD would need to be checked separately against CASA’s public AD records; no such amendments are recorded in the text supplied.

The AD document supplied does not include, reference or summarise any litigation, appeals, or court decisions arising from its issuance. It contains no mention of legal challenges, reviews, or administrative appeals in relation to AD/BAe 146/122.

What the document does provide that might be relevant in a litigation context:

• A clear statement of the technical requirement and compliance dates: The AD specifies the mandatory replacement, the SB to be used, the effective date and the compliance date (Requirement; Compliance; Effective date). Those documented elements would be the factual basis for any regulatory compliance dispute but the AD itself contains no narrative or footnote about subsequent legal proceedings.

• A link to EASA action: The AD states “Note: EASA AD 2006‑0137 dated 23 May 2006 refers” (Requirement note). If litigation or dispute arose that involved international regulatory coordination, the referenced EASA AD could be a source of material evidence or comparative regulatory standards, but the AD text does not narrate any litigation around that cross‑reference.

The absence of litigation material in the AD means that any researcher seeking litigation history would need to consult external sources,court databases, CASA public records, or legal reporting services,to determine whether any enforcement action or legal challenge followed this AD. The AD itself neither records nor claims any such history.

The AD is short and specific, but its brevity leaves several practical pitfalls and traps for those implementing or advising on compliance. The following are concrete issues drawn from the AD text that practitioners and operators should be attentive to.

1. Replacement required, not inspection or re‑orientation:

• The AD “requires the replacement of the existing nose wheel abutment rings with revised nose wheel abutment rings” (Background; Requirement). An operator that assumes a quick inspection or a re‑orientation of existing rings will suffice is mistaken: the text mandates replacement, not merely inspection or correction.

2. Narrow technical reference , use the correct SB or later EASA‑approved revision:

• Compliance is “per SB 32‑174‑70676A Initial issue or later EASA approved revision” (Requirement). Using an earlier or different SB, or a workshop practice that departs from the SB, risks non‑compliance. Equally, using an SB revision that is not EASA‑approved would be outside the explicit permissions of the AD.

3. Timing window management:

• The AD becomes effective 3 August 2006 but requires completion “Prior to 31 May 2007” (Compliance; Effective date). Operators may confuse the effective date with last practicable compliance date; the correct interpretation is that the AD is binding as from 3 August 2006 and the work must be finished before the stated compliance date. Scheduling constraints, availability of parts or shop slots between those dates could create logistical pressure.

4. Parts supply and lead times:

• The AD requires “revised nose wheel abutment rings” (Background; Requirement). If revised parts are in limited supply, operators who wait too long may face delays that risk falling past the compliance date. The AD does not provide for extensions or phased compliance; the obligation is to complete the replacement before the deadline.

5. Cross‑reference to EASA AD:

• The AD “refers” to “EASA AD 2006‑0137 dated 23 May 2006” (Requirement note). Practitioners should not assume that the CASA AD is the entirety of the applicable rules; they should check the EASA AD for any additional technical or administrative instructions. Conversely, relying solely on the EASA AD without ensuring full compliance with the CASA AD’s stated SB requirement could be risky.

6. Certification and documentation not specified:

• The AD does not set out what paperwork constitutes proof of compliance. Operators must ensure maintenance releases and aircraft records document the replacement and reference AD/BAe 146/122 and the SB used for compliance. Failure to create auditable records is a practical compliance risk, even though the AD does not specify forms.

7. No explicit alternative means of compliance offered:

• If an operator believes another mitigation is technically equivalent (for example a redesign or retrofit from a third party), the AD text does not describe a process for CASA acceptance of an alternative. Any alternative method is therefore procedurally uncertain absent separate regulatory approval.

8. Scope: “All Models” catch:

• The AD’s applicability is broad: “All Models BAe 146 and AVRO 146‑RJ series aeroplanes” (Applicability). This captures every variant in those families; owners may misread applicability and exclude some serials or sub‑variants in error. Confirm the model designation matches the aircraft registration and type design data.

9. Danger of misinterpreting the safety net of the revised ring:

• The AD emphasises that the revised ring will “prevent the nose wheel retaining nut from engaging with the axle threads” if fitted incorrectly (Background). That is a design fail‑safe, but it does not remove the need for correct installation and maintenance discipline. Operators should not rely on the revised ring as a substitute for competent maintenance practice.

10. No mention of immediate grounding or interim measures:

• The AD does not state whether aircraft may continue to operate pending replacement up to the compliance date or whether immediate grounding is required. Operators should treat the AD requirement as mandatory but will need to reconcile operational decisions (for example whether to ferry aircraft for maintenance) with their own safety management systems and any CASA guidance not contained in the AD.

These “gotchas” arise from the AD’s design: a short, technical mandate that fixes a required part replacement but leaves administrative, record‑keeping, and alternative approval procedures to the broader regulatory framework or to operator practice. Practitioners should plan for parts procurement, shop capacity and clear documentation well in advance of the compliance deadline.

The AD prescribes a single, narrow route to compliance. The following is a practical, step‑by‑step checklist rooted in the AD text, together with administrative steps that the AD itself does not specify but which are necessary to demonstrate and sustain compliance in normal continuing airworthiness practice.

1. Confirm applicability

• Verify that each aircraft in the operator’s fleet falls within the AD’s scope: “All Models BAe 146 and AVRO 146‑RJ series aeroplanes” (Applicability). Match the aircraft type designation in the flight log or certificate of airworthiness to the AD’s applicability statement.

2. Obtain the governing technical documentation

• Acquire “SB 32‑174‑70676A Initial issue” and check whether a later EASA‑approved revision exists. The AD permits compliance “per SB 32‑174‑70676A Initial issue or later EASA approved revision” (Requirement). If a later EASA‑approved revision is available, obtain and use that latest EASA‑approved version.

3. Review the referenced EASA AD

• The AD notes “EASA AD 2006‑0137 dated 23 May 2006 refers” (Requirement note). Obtain and review the EASA AD to ensure there are no additional instructions, parts numbers, or clarifications that affect how the SB must be implemented for cross‑jurisdictional conformity.

4. Plan maintenance scheduling within the compliance window

• The AD sets the effective date and the deadline: it “becomes effective on 3 August 2006” and compliance is required “Prior to 31 May 2007” (Compliance; Effective date). Schedule aircraft down‑time, parts procurement, and MRO capacity to ensure the work is completed before the deadline.

5. Order revised parts

• Procure the “revised nose wheel abutment rings” specified in the SB and ensure they conform to the design intent stated in the AD , namely that if fitted incorrectly they “will prevent the nose wheel retaining nut from engaging with the axle threads” (Background). Confirm part numbers and conformity paperwork from the supplier.

6. Perform the replacement to the SB

• Have a suitably authorised maintenance organisation carry out the replacement “per SB 32‑174‑70676A” or the later EASA‑approved revision (Requirement). Ensure that the SB’s procedural steps are followed exactly, that authorised tools and torques are used, and that any additional inspections mandated by the SB are performed.

7. Post‑work verification and release to service

• After completion of the SB procedures, the maintenance organisation should perform whatever verification and functional checks the SB requires, then issue the maintenance release. The AD does not set out a specific verification regime, so rely on the SB’s post‑installation checks.

8. Record keeping and AD compliance trace

• Document the compliance action in the aircraft’s maintenance log and continuing airworthiness records. Record the AD reference (AD/BAe 146/122), the SB used (including revision and approval status), part numbers installed, serial numbers where applicable, and dates of work. While the AD does not specify forms, an auditable record is necessary to evidence compliance to CASA or third parties.

9. Communicate with airworthiness authorities where necessary

• If an operator intends to propose an alternative method of compliance or cannot meet the compliance deadline for reasons beyond its control, seek formal guidance or approval from CASA. The AD itself does not describe an alternative compliance route or extension process.

10. Monitor supplier and SB revisions

• Because the AD permits “later EASA approved revision” of the SB, continue to monitor EASA and the SB issuer for revisions up to the date of compliance. If a later EASA‑approved revision changes procedures or part numbers, adopt the later revision as permitted by the AD.

11. Operational decisions pending compliance

• The AD does not state whether aircraft may remain in service up to the compliance date; operators should, consistent with their Safety Management System and the SB’s interim provisions (if any), make conservative decisions about operating aircraft that still have original rings. Consider ferry flights limited to maintenance relocation in accordance with crew and airworthiness safety assessments.

12. Liaise with insurers and lessors where applicable

• For leased aircraft, confirm responsibility for the replacement (cost allocation) and ensure the lessor is informed of the compliance plan and recorded completion. The AD itself does not allocate financial responsibility; contractual arrangements will govern who pays.

By following these steps,confirm applicability, obtain the right SB revision, procure parts, schedule and perform the SB work, issue appropriate maintenance releases and records, and ensure communications with regulatory and contractual stakeholders,an operator can satisfy the AD’s express requirements. The AD’s brevity places weight on the SB for technical detail and on the operator to produce the administrative evidence of compliance.