AD/BAe 146/119 - Hydraulic System - Accumulators with Suspect Defect

The AD rests on a small set of tightly framed technical and procedural concepts. These concepts drive what operators must do, and how the manufacturer’s ISB and the EASA emergency AD plug into the national directive.

• Applicability: The AD applies to BAe 146 and AVRO 146‑RJ series aircraft produced by BAE SYSTEMS. The source lists the applicability header explicitly: “BAE SYSTEMS - BAe 146 and AVRO 146‑RJ series aircraft.” That is the defined scope of aircraft to which its requirements attach.

• Suspect batch identification: The AD requires identification of accumulators from two suspect batches as identified in BAE Systems ISB.29‑A046 initial issue dated 14 March 2006 or later EASA‑approved revisions (Requirement). The ISB is the technical reference that operational crews and maintenance organisations must use to identify which accumulators are suspect.

• Installation limit: The AD imposes an operational constraint on equipment state: “Only one suspect accumulator is allowed to be installed on an individual aircraft” (Requirement item 1). That creates an immediate asset management requirement where operators must determine the batch status of installed accumulators.

• Inspection regime: Where a suspect accumulator is present, the AD mandates inspection “in accordance with ISB.29‑A046” (Requirement item 2) and establishes a repetitive inspection cadence: inspections at 48‑hour intervals until the terminating action is performed (Compliance item 2).

• Replacement and terminating action: The AD requires replacement of identified accumulators in accordance with paragraph 2.D of ISB.29‑A046 (Requirement item 3). The AD then states that replacement of the identified accumulator with a serviceable accumulator “is considered terminating action from the requirements of this AD.” The AD also sets an absolute latest date for compliance with a replacement requirement: “Not later than 31 May 2006” (Compliance item 3).

• Temporal urgency and authority linkages: The AD is time‑sensitive (effective 23 March 2006; initial action within 48 hours), and it expressly refers to an EASA Emergency AD (2006‑0061‑E dated 17 March 2006) which appears to be the originating emergency action that prompted the national AD.

• Hazard definition: The AD defines the hazard in concrete terms: accumulator burst risk may cause loss of one or more hydraulic circuits, increased flight crew workload, possible fuselage pressure vessel rupture, and possible cabin contamination with hydraulic mist. The AD frames these as a hazardous event with “an unacceptable probability of occurrence” following an in‑service failure and subsequent identification of suspect batches.

Mechanically, the AD binds operational and maintenance behaviour to the manufacturer’s inspection and replacement procedures. The core decision nodes for an operator are: (a) identify whether the aircraft has an accumulator from a suspect batch, (b) if so, carry out the ISB inspections at 48‑hour intervals until replacement, and (c) replace the accumulator per ISB para 2.D by the absolute date specified. The AD thus converts a manufacturer's technical bulletin into mandatory, time‑bound regulatory obligations.

The AD directly affects operators and maintainers of BAE SYSTEMS BAe 146 and AVRO 146‑RJ series aircraft. The Applicability section is explicit: the AD applies to those aircraft series. That means registered operators, maintenance organisations, and the airworthiness managers responsible for those aircraft must act to meet the AD’s requirements.

Who pays: The source text does not allocate costs, but the operational implications show where costs will fall. Identification, inspection and replacement tasks are operational and maintenance activities that are typically performed by the aircraft operator or their contracted maintenance organisation. Therefore, the operator will bear the direct costs of locating suspect accumulators, performing inspections at the specified 48‑hour intervals, and procuring and fitting serviceable replacement accumulators in accordance with ISB.29‑A046 para 2.D. The AD does not mention any public funding or cost‑sharing mechanism.

Who decides and issues the requirement: The AD document is issued under the authority of the Civil Aviation Safety Authority (CASA), signed by a CASA delegate (Charles Lenarcic), which indicates the national regulator has mandated the action. The AD also references an EASA Emergency AD (2006‑0061‑E), indicating coordination or reliance upon European Aviation Safety Agency emergency findings. The AD requires use of the BAE Systems ISB and allows later EASA‑approved revisions of that ISB to be used.

Operational impact on scheduling and utilisation: The AD’s compliance timelines are acute. It requires initial identification actions within 48 hours of the AD’s effective date (Compliance item 1). Where a suspect accumulator is identified, inspections must be repeated every 48 hours until replacement (Compliance item 2), creating an ongoing inspection burden until the terminating action. There is also a hard replacement date (“Not later than 31 May 2006,” Compliance item 3), which compresses scheduling, spares planning and maintenance shop time into a limited window.

Maintenance organisations: Licensed maintenance organisations and certifying staff responsible for airworthiness approvals will need to follow the ISB’s prescribed inspection and replacement procedures. The AD itself leaves the ISB as the technical standard to be followed; the AD does not specify which certifying authority or licence class must perform the inspections, but the instruction “inspect … in accordance with ISB.29‑A046” delegates method and standards to the manufacturer’s procedure.

Passengers, insurers and lessors: The AD imposes a safety mitigation that could affect operational availability. The source does not mention insurance or lease arrangements, but lessors or insurers will have an interest in compliance status because the AD addresses a failure mode with potential fuselage pressure vessel rupture and cabin contamination. The AD text itself does not allocate responsibilities among operators, lessors or insurers.

Third parties and supply chain: The AD creates concentrated demand for serviceable accumulators and may require sourcing parts consistent with ISB para 2.D. The AD does not specify parts provenance or approved suppliers; it simply requires replacement consistent with the ISB instructions.

The AD imposes specific duties on operators and maintenance personnel and articulates the method for terminating the AD’s obligations. The duties are procedural and time‑limited. The AD does not posit rights in the sense of exemptions or appeals within the text; it focuses on required actions and timing.

Primary duties (as stated in the Requirement and Compliance sections):

• Identify suspect accumulators: Operators must identify suspect batch number accumulators “in accordance with BAe 146 series / Avro 146‑RJ series aircraft Inspection Service Bulletin ISB.29‑A046 initial issue dated 14 March 2006 or later EASA approved revisions.” The duty is to use that ISB as the identification method (Requirement item 1).

• Limit installations: Once identified, an operational restriction is imposed: “Only one suspect accumulator is allowed to be installed on an individual aircraft” (Requirement item 1). This is an ongoing constraint until the accumulator is replaced and the AD is terminated for that aircraft.

• Inspect suspect accumulators: Where a suspect accumulator is identified, the AD requires inspection “in accordance with ISB.29‑A046” (Requirement item 2). The Compliance section prescribes that these inspections must occur repetitively at 48‑hour intervals “until terminated as detailed in ISB.29‑A046” (Compliance item 2).

• Replace identified accumulators: The AD requires replacement “in accordance with para 2.D. of ISB.29‑A046” (Requirement item 3). Replacement with a serviceable accumulator is explicitly designated as the terminating action from the AD’s requirements.

• Timing duties: Initial identification/inspection action must occur “within 48 hours after the effective date of this AD” (Compliance item 1). The repetitive inspections are at 48‑hour intervals (Compliance item 2). There is a final compliance deadline of “Not later than 31 May 2006” (Compliance item 3), which the AD places against the required replacement obligation.

Rights and procedural clarifications in the AD text:

• Use of later EASA‑approved revisions of the ISB: The AD allows the use of “later EASA approved revisions” of ISB.29‑A046 for identification and inspection methods. That operates as a limited procedural right to rely on updated EASA‑approved versions of the ISB rather than being frozen to the initial issue.

• Termination: Replacement with a serviceable accumulator is the AD’s stated terminating action; this is the explicit mechanism by which an operator discharges ongoing inspection obligations. The AD does not describe administrative procedures for notifying the regulator that terminating action has been completed; nor does the AD in the supplied text provide an exemption or relief process.

What the AD does not say about duties and rights:

• The AD does not specify who must perform the inspections or replacements (for example, whether a particular licence category of engineer is required). It only prescribes the technical standards to follow (the ISB).

• The AD does not set out enforcement processes, reporting obligations or recordkeeping specifics in the provided text. It also does not state any appeal procedure against the AD within its own text.

• The AD does not allocate costs, reimbursements, or supply arrangements for replacement parts. Operators therefore face direct commercial consequences without statutory cost allocation in the text.

The AD text supplied does not set out penalties, enforcement mechanisms, or administrative sanctions. It functions as a prescriptive airworthiness directive with mandatory requirements (identification, inspection, replacement and timing), but it contains no express penalty clause, infringement fine schedule, or enforcement procedure in the provided content.

What the AD does specify that bears on enforcement risk:

• The AD has explicit, time‑bound obligations. It becomes effective on 23 March 2006, requires initial action within 48 hours, repetitive inspections every 48 hours where a suspect accumulator is present, and replacement no later than 31 May 2006. These deadlines create clear compliance metrics against which an operator’s conduct can be judged.

• The AD references the manufacturer’s ISB and an EASA Emergency AD. These cross‑references tie the AD to internationally recognised technical standards and an earlier emergency finding by EASA. That connection may strengthen a regulator’s case that the AD was reasonable and technically mandated.

Matters not addressed in the AD text:

• The instrument does not state which regulatory statute or enforcement powers underpin the AD. The signature block shows a delegate of the Civil Aviation Safety Authority issued it, but the AD does not reproduce the specific legal authority for issuing the directive, nor does it outline the sanctions for non‑compliance in this text.

• There is no explicit requirement in the AD text for reporting inspection results to the regulator, nor any direction about mandatory notification of replacement completion. The AD does not list administrative processes such as submission of compliance paperwork, nor does it cite penalty amounts or types of enforcement (suspension of certificate, grounding, fines).

Practical enforcement implications (limited to what the source supports):

• Because the AD imposes mandatory technical steps and definitive deadlines, non‑compliance would be measurable by comparing work records and maintenance logs to the AD’s timing and procedural instructions. The AD’s lack of internal penalty language does not mean non‑compliance is consequence‑free; regulators commonly have powers to enforce ADs under broader statutory regimes, but those powers and processes are not described in the supplied text.

• The AD’s reference to EASA emergency AD 2006‑0061‑E suggests coordination with EASA findings; this may increase regulatory expectations for adherence, particularly where an emergency AD has been issued by a regional authority.

In short, the AD itself prescribes obligations but does not specify in this text the punitive mechanisms or administrative enforcement steps that will be used if an operator fails to comply. Those enforcement mechanisms, if they exist, sit outside the AD’s text as provided.

The AD explicitly references external technical and regulatory documents and situates itself within international emergency action. The interactions disclosed in the source are primarily with the manufacturer's inspection service bulletin and an EASA emergency AD.

• Manufacturer’s ISB as operational standard: The AD requires identification, inspection and replacement actions “in accordance with BAe 146 series / Avro 146‑RJ series aircraft Inspection Service Bulletin ISB.29‑A046 initial issue dated 14 March 2006 or later EASA approved revisions.” This means the AD delegates the technical method for compliance to the manufacturer’s ISB and allows later EASA‑approved revisions of that ISB to be used. The AD therefore interacts with and relies on the content and revisions of the ISB as the normative technical standard.

• EASA Emergency AD: The AD states in its note that “EASA Emergency AD number 2006‑0061‑E dated 17 March 2006 refers.” That shows a direct cross‑reference to an EASA emergency directive that preceded or coincided with this national AD. The AD thus links national regulatory action to an EASA emergency finding. The AD permits the use of EASA‑approved revisions of the ISB, reinforcing the linkage.

• Temporal sequencing and precedence: The AD became effective on 23 March 2006, while the ISB initial issue is dated 14 March 2006 and the EASA emergency AD is dated 17 March 2006. That sequence suggests the national AD follows a manufacturer identification of suspect batches and a contemporaneous EASA emergency response. The AD adopts the ISB methods and EASA’s emergency action as the bases for mandatory national compliance.

• No explicit mention of broader aviation legislation or enforcement powers: The supplied AD text does not reproduce the statutory provision under which the AD is issued, nor does it reference national aviation safety legislation, enforcement codes, or criminal statutes. It is therefore silent on how it fits procedurally into enforcement under national law. Nevertheless, the document’s issuance by a CASA delegate indicates it is a regulatory instrument under the national aviation safety regime, but the AD does not itself spell out the interaction with the statute or enforcement framework.

• Interaction with maintenance and airworthiness records: The AD mandates actions to be performed “in accordance with ISB.29‑A046” but does not in this text specify recordkeeping, reporting, or certification steps. Any interaction with legal obligations to maintain maintenance logs, carry out approvals, or report occurrences would exist in the broader regulatory framework but is not set out in the supplied AD text.

• Parts and supplier approvals: The AD requires replacement “in accordance with para 2.D. of ISB.29‑A046,” but it does not itself list approved parts or suppliers. The interaction, therefore, is operational: the ISB likely contains parts and procedural specifics; the AD ties legally mandatory compliance to those details, and any statutory regimes controlling parts approvals would interact through the ISB and operator practices rather than through the AD text.

In summary, the AD interacts directly with the manufacturer’s ISB and EASA’s emergency AD; it does not set out, within its own text, the statutory authority or the enforcement regime that would give effect to the AD under national law.

The document supplied contains limited amendment history and dated references which indicate a short window of related publications. The relevant dated items and revision permissions in the AD text are:

• ISB date: The AD requires identification and inspection “in accordance with … ISB.29‑A046 initial issue dated 14 March 2006 or later EASA approved revisions.” That establishes 14 March 2006 as the initial ISB date and explicitly allows later EASA‑approved revisions to be used for compliance. The AD therefore permits subsequent ISB revisions that obtain EASA approval to be followed in lieu of the initial issue.

• EASA Emergency AD reference: The AD notes “EASA Emergency AD number 2006‑0061‑E dated 17 March 2006 refers.” That provides a clear cross‑reference to a European emergency AD dated 17 March 2006. It may be read as the proximate international emergency action to which this national AD responds.

• AD effective date: The AD states it “becomes effective on 23 March 2006.” The signature block shows the AD was signed on 21 March 2006 by a CASA delegate (Charles Lenarcic). The AD identification is AD/BAe 146/119 and indexed as 5/2006 TX.

• Compliance deadlines: The Compliance section prescribes initial action within 48 hours after the effective date (i.e. within 48 hours of 23 March 2006) and a final replacement deadline “Not later than 31 May 2006.” Those dates establish the operational timeline within which actions must be completed. The AD itself does not provide a record of prior versions or amendments to the AD; it includes permission to use later EASA‑approved ISB revisions but does not list any AD amendments after its issuance.

• No later amendments recorded in source: The supplied text contains no subsequent amendment notices, corrigenda, superseding AD numbers, or revocations. The AD’s language allowing “later EASA approved revisions” of the ISB to be used is the only provision that expressly facilitates change in compliance methodology without amending the AD itself.

Therefore, the amendment history within the supplied source is limited to: the initial manufacturer ISB dated 14 March 2006, the EASA emergency AD dated 17 March 2006, the national AD signature and issuance on 21-23 March 2006, and a replacement completion deadline of 31 May 2006. The AD explicitly contemplates use of later EASA‑approved ISB revisions but does not itself record any post‑issuance amendments in the provided text.

The supplied AD text contains no litigation history. There are no references to judicial review, appeals, disputes, enforcement actions, or court decisions in the document. The AD is an administrative instrument signed by a CASA delegate (Charles Lenarcic) and dated 21 March 2006; beyond that signature and the technical attachments (the ISB and EASA emergency AD reference), the text does not record any contested proceedings or legal challenges.

Implications of absence of litigation history in the text:

• The lack of litigation references in the AD is not evidence that the AD was not or could not be litigated; it simply indicates the AD document does not summarise or record any subsequent or contemporaneous litigation. Any judicial or administrative challenges, enforcement proceedings, or compliance disputes would lie in external records and are not contained in the source.

• For practical purposes, lawyers, compliance officers and operators must treat the AD’s requirements as regulatory obligations while recognising that the supplied text does not provide insight into how the regulator has enforced the AD in practice, or whether any disputes arose about the AD’s scope, timelines, or technical content.

• Where litigation occurred outside the AD text, it would not be visible here. The AD itself contains specific, measurable compliance obligations (identification, inspection cadence, replacement and terminating action) that could form the basis of enforcement or disputes, but any such events are beyond the scope of the document supplied.

In short, there is no litigation history included in the source to cite or analyse.

The AD’s brevity and reliance on the manufacturer’s ISB create several practical pitfalls and interpretative risks that practitioners should note. These are drawn directly from the AD wording and the timing constraints it sets.

• Tight timeframes: The AD became effective on 23 March 2006 and requires initial action “within 48 hours after the effective date” (Compliance item 1). That creates a short operational window for identification tasks. Operators that do not triage their BAe 146/Avro 146‑RJ fleet quickly risk missing the 48‑hour window and creating measurable non‑compliance.

• Repetitive 48‑hour inspection cadence: If a suspect accumulator is identified, inspections must be performed repetitively every 48 hours “until terminated as detailed in ISB.29‑A046” (Compliance item 2). That cadence can be operationally taxing: it implies recurrent maintenance interventions while an aircraft remains in service, requiring planification of maintenance slots, possible flight cancellations if inspections cannot be performed between flights, and recordkeeping to demonstrate the inspections occurred at the required intervals.

• “Only one suspect accumulator” rule: The AD states “Only one suspect accumulator is allowed to be installed on an individual aircraft” (Requirement item 1). This requires immediate verification of accumulator batch numbers for all units on an aircraft. The AD does not specify how many accumulators are normally installed on these aircraft types, so operators must verify each accumulator’s batch status. Failure to do so may result in aircraft being non‑compliant by having more than one suspect accumulator installed.

• Replacement as terminating action and absolute deadline: Replacement with a serviceable accumulator is “considered terminating action from the requirements of this AD.” The Compliance section also includes a calendar‑date requirement: “Not later than 31 May 2006” (Compliance item 3). That imposes a hard deadline for replacing identified accumulators. If serviceable spare accumulators are scarce, operators must secure spares promptly to avoid prolonged inspection regimes and potential operational constraints.

• Reliance on ISB and EASA approvals: The AD requires actions “in accordance with ISB.29‑A046 initial issue dated 14 March 2006 or later EASA approved revisions.” Practically, that means the ISB’s contents and any EASA‑approved revisions become the operative technical standard. If the ISB’s instructions are ambiguous, inconsistent with operator procedures, or require parts or techniques not standard in a particular maintenance organisation, the AD does not itself provide fallback technical detail; operators must rely on the ISB and any EASA‑approved updates.

• Ambiguity about who performs inspections and what constitutes compliance evidence: The AD does not specify which certifying personnel or organisation must carry out the inspections or how compliance reporting should be done. Operators must interpret the applicable national maintenance and certification rules to determine the appropriate license category and sign‑off requirements. The absence of an explicit reporting channel in the AD means operators should proactively document compliance in maintenance records and, if in doubt, liaise with the regulator.

• Possible ambiguity in Compliance item numbering: The AD sets out three Compliance items after three Requirement items. The AD’s formatting separates the list, and while the natural reading is that Compliance item 3 corresponds to the replacement requirement (Requirement item 3), practitioners should check the ISB and any guidance from CASA or the manufacturer for clarity on the replacement deadline and its application to individual aircraft cases.

• Safety hazard specifics: The Background section describes potential outcomes including fuselage pressure vessel rupture and cabin contamination with hydraulic mist. The AD’s identification of these specific hazards should prompt safety managers to consider immediate risk mitigations for passenger safety, smoke/contamination procedures and cockpit workload impacts in event of hydraulic circuit loss. The AD does not prescribe operational mitigations beyond inspection and replacement, so operators must integrate the AD tasks into their safety management and operational risk profiles.

• No mention of documentation or reporting obligations: The AD does not instruct operators to report inspection results to CASA or BAE Systems. If operators rely solely on internal records without external notification, regulators or other stakeholders may be unaware of fleet compliance status. Operators should therefore consider proactive communications with their competent authority if there is any ambiguity.

• Supply chain pressure: The AD’s replacement deadline and the likely simultaneous demand across multiple operators could create spare part shortages. The AD contains no provisions for alternative parts, authorisations for non‑standard parts, or special sourcing approvals. Operators may face lead‑time risk in obtaining serviceable accumulators.

These “gotchas” are operational and legal friction points implied by the AD’s wording and timing. They are not additional regulatory requirements; they are practical issues that arise from the AD’s structure and reliance on an external ISB and an EASA emergency AD.

Below is a practical, source‑grounded checklist for satisfying the AD’s requirements, strictly tied to the text of the directive and its cross‑references. The steps assume the operator is responsible for compliance and that the operator will coordinate with their maintenance organisation.

1. Obtain the controlling technical documents:

   • Acquire BAE Systems Inspection Service Bulletin ISB.29‑A046 initial issue dated 14 March 2006. The AD permits use of “later EASA approved revisions,” so also check for any EASA‑approved ISB revisions and obtain the latest EASA‑approved issue before performing work (Requirement and note on revisions).

2. Confirm the AD’s timelines and effective date:

   • Note the AD effective date: 23 March 2006, and the requirement to take initial action “within 48 hours after the effective date of this AD” (Compliance item 1). Ensure planning accounts for that 48‑hour initial window and the repetitive 48‑hour inspection cadence where a suspect accumulator is found (Compliance item 2).

3. Identify installed accumulators:

   • Using the ISB.29‑A046 identification procedures, inspect the aircraft to identify any accumulator batch numbers matching the suspect batches described in the ISB (Requirement item 1). Confirm that no more than one suspect accumulator is installed on each aircraft; if multiple suspect accumulators are present, plan immediate corrective action to comply with the “only one” rule.

4. If a suspect accumulator is identified:

   • Carry out the ISB‑specified inspection procedure for that accumulator (Requirement item 2). The AD requires inspections “in accordance with ISB.29‑A046” and instructs repetitive inspections at 48‑hour intervals “until terminated as detailed in ISB.29‑A046” (Compliance item 2). Organise maintenance slots or line maintenance procedures to perform the inspections at the 48‑hour interval reliably.

5. Replace identified accumulators:

   • Replace the identified suspect accumulator “in accordance with para 2.D. of ISB.29‑A046” (Requirement item 3). The AD states explicitly that “Replacement of identified accumulator with serviceable accumulator is considered terminating action from the requirements of this AD.” Ensure replacement parts meet the ISB’s criteria for “serviceable accumulators.”

6. Meet the calendar deadline:

   • Ensure that replacement is completed “not later than 31 May 2006” (Compliance item 3). If spare parts are not on hand, expedite procurement to meet this absolute date; do not rely on the AD continuing indefinitely without replacement.

7. Use EASA‑approved ISB revisions where appropriate:

   • If an EASA‑approved revision of ISB.29‑A046 exists, it is acceptable to use the later revision for identification, inspection and replacement, per the AD’s permission. Confirm any changes in procedures or parts listed in the revision and apply them.

8. Document compliance:

   • Although the AD text does not specify report or record filing obligations, maintain contemporaneous maintenance records showing: (a) identification checks and results, (b) dates and results of the 48‑hour inspections while a suspect accumulator remained installed, (c) the replacement action including part numbers and installation records, and (d) any deviations or delays with justification. These records will be the primary evidence of compliance with the AD’s timing and technical requirements.

9. Coordinate with regulator and manufacturer as needed:

   • Where there is any uncertainty in ISB interpretation, consider contacting the regulator (CASA) or BAE Systems for clarification. The AD references EASA AD 2006‑0061‑E; if cross‑jurisdictional operations are involved (for example, aircraft operating in EASA states), coordinate compliance approaches and chosen ISB revision acceptance with the relevant authorities.

10. Operational contingency planning:

    • Given the hazard description (possible loss of hydraulic circuits, fuselage pressure vessel rupture, cabin contamination), integrate AD compliance with operational safety procedures. If an inspection reveals evidence of imminent failure, remove the aircraft from service immediately and follow emergency procedures.

11. Spare parts and supply management:

    • Anticipate increased demand for serviceable accumulators and source parts in advance. Verify parts meet the ISB’s requirements and that installation is performed by appropriately qualified maintenance staff consistent with the ISB and national maintenance regulations.

12. Internal responsibility allocation:

    • Assign clear roles within the operator and maintenance organisation for (a) identification and record checks of accumulator batch numbers, (b) scheduling and performing inspections at 48‑hour intervals, and (c) arranging and documenting replacement by 31 May 2006.

This compliance checklist maps directly to the AD’s text: identification per ISB (Requirement item 1), inspections per ISB and at 48‑hour intervals (Requirement item 2; Compliance item 2), replacement per paragraph 2.D and by 31 May 2006 (Requirement item 3; Compliance item 3), and the allowance of later EASA‑approved ISB revisions. Operators should ensure their maintenance records can demonstrate adherence to the AD’s timing and technical requirements in the event of regulatory audit.