Skip to content

Airbus A330 records

Airbus A330 family Airworthiness Directive status records review

This review tests whether the Airworthiness Directive status list for an Airbus A330 is supported by the evidence behind each line. It is run for a lessor, operator, or acquirer who needs the AD position to hold under an auditor or a buyer. It works through applicability for the serial number, the accomplishment record for each open and closed directive, and the method of compliance claimed. You receive an exception list of unsupported or misapplied AD lines, a source map tying each position to its evidence, and a plan to close the gaps on this asset.

When this review is needed

  • An A330 is changing hands and the buyer will test the AD position line by line against evidence.
  • The status list was generated by a tracking system and its accomplishment backing has never been verified.
  • The aircraft is moving between FAA and EASA oversight and applicability has to be re-read for the receiving state.
  • An auditor flagged AD lines closed without the underlying accomplishment record on file.

The problem

An AD status list reads as settled until someone asks for the record behind a closed line. On a long-haul A330 the directive population is large and layered with revisions, superseded actions, and repetitive inspections, so a line marked complete may rest on a work order that never made it into the file. Applicability adds a second trap: a directive can be closed as not applicable on the basis of a configuration the aircraft no longer, or never, held.

What gets reviewed

  • AD applicability determined against the actual configuration and effectivity of the serial number
  • Accomplishment evidence located for each directive marked complete
  • Method of compliance confirmed for each closed line, including terminating action where claimed
  • Repetitive inspection intervals checked against the last accomplishment and current status
  • Superseded and revised directives reconciled so the list reflects the governing revision
  • Open directives carried with their next-due basis rather than left ambiguous

Scope this review

Tell us the asset, the event, and the evidence in scope, and we will outline a focused first engagement.

Send a representative, redacted record set and we will scope the review.

What gets validated

  • Each closed AD line is backed by a work order or record showing what was actually done
  • Not-applicable dispositions rest on the configuration the aircraft holds, not a generic fleet assumption
  • Terminating actions are supported by the modification or repair record that ends the repetitive requirement
  • Repetitive inspection intervals are computed from the last accomplishment on this aircraft
  • The list reflects the current directive revision rather than a superseded issue

Evidence normally required

  • The current AD status list for the serial number
  • Accomplishment records, work orders, and compliance certifications behind the closed lines
  • The configuration and modification status that governs applicability
  • The directive source texts for the governing state of registry
  • Prior audit findings on the AD position, if any exist

Common discrepancies

  • A directive marked complete whose accomplishment record is not in the file
  • A not-applicable disposition based on a configuration the aircraft does not hold
  • A repetitive inspection whose interval was tracked from the wrong reference point
  • A superseded directive still shown as the governing action on the list

What is at stake

AD lines taken on trust at closing become the new owner's exposure the moment an authority or a downstream buyer asks for proof. A misread applicability can hide an open action that surfaces as a grounding item, and a repetitive inspection tracked to the wrong interval can drift out of compliance without any entry showing it.

Move from findings to resolution

Move from findings to a documented resolution path.

How the work runs

01

Fix applicability

Read each directive against the serial number's configuration and effectivity before scoring status.

02

Find the evidence

Locate the accomplishment record behind every closed and terminated line.

03

Check the repetitives

Recompute repetitive inspection intervals from the last accomplishment on this aircraft.

04

List the exceptions

Report unsupported and misapplied lines with the evidence needed to close them.

What the buyer receives

  • An exception list of unsupported, misapplied, or superseded AD lines
  • A source map linking each verified position to its accomplishment evidence
  • A closure plan sequencing the evidence retrieval and applicability corrections

Who uses the output

  • Asset managers pricing the AD exposure the records actually support
  • Continuing-airworthiness teams closing the unsupported lines before the next check
  • Buyers confirming the directive position holds before they rely on it

How the work fits into the transaction or program

The AD review depends on a settled configuration baseline, because applicability is read off it, and feeds the status position a transaction or an induction rests on. Its exception list drives remediation while the seller still holds the records and the people who accomplished the work.

Aircraft-specific considerations

A330 AD exposure tracks the asset's long-haul history: heavy utilization drives repetitive inspection cycles, and engine shop-visit depth and cabin reconfigurations change which directives apply. A serial number that has passed through several operators carries more revision layers and more places for an applicability call to have detached from the current configuration.

Jurisdiction-specific considerations

An A330 moving between FAA and EASA oversight requires the directive population to be re-read for the receiving authority, because a directive applicable under one state may be addressed differently or superseded under the other. The review notes where applicability and method of compliance need rework for the receiving system.

Regulatory limits

The review reconciles the AD list against the evidence and the governing directives. It does not accomplish any directive, issue a compliance finding on an authority's behalf, or make an airworthiness determination on the aircraft.

What this review does not cover

Specific to this review

  • Applicability, not accomplishment, is where A330 AD lists most often fail, because a not-applicable call rides on a configuration that has since changed.
  • Repetitive inspection intervals on a high-utilization A330 drift quietly when the interval is counted from a fleet reference instead of the last accomplishment on the tail.
  • A terminating action closes a repetitive requirement only if the modification behind it is traceable, so an unrecorded embodiment reopens an AD that looked closed.

Sources

Frequently asked questions

Why re-check applicability if the tracking system already scored the AD?

Tracking systems apply directives against a stored configuration that can lag the aircraft. A modification embodied or removed after the record was set can change applicability, so the position is re-read against the configuration the A330 actually holds.

Relevant glossary terms

Related pages

Where this fits

Talk to an engineer who has done this work

We will walk through your current state, the records or evidence involved, and a scoped first engagement.

Talk through the aircraft, records, evidence, deadline, and next useful step.