Skip to content

Configuration records

Equipment list and configuration records review within the continuing-airworthiness source file

An equipment list source review confirms that the aircraft equipment list still describes the aircraft the CAMO file describes. Working from status reports, airworthiness-review notes, program references, and the open-item log, the analyst checks each list entry for a matching installation record, release document, and approval where the item was added or changed by modification. Entries the file cannot support, and installed items the list never picked up, are written into an exception list for the continuing-airworthiness manager. It is commissioned when the airworthiness status baseline is set, refreshed, or challenged.

When this review is needed

  • Component swaps during line maintenance have outpaced the equipment list revision cycle for months.
  • A modification campaign changed installed equipment and the list was updated from the plan rather than from the as-built result.
  • Inbound transition records include an equipment list whose revision date predates several documented removals.
  • Rotable pooling or loan arrangements have put units on the aircraft that the operator's own records never formally received.

The problem

Equipment lists decay at the speed of line maintenance. Every removal and installation is individually recorded somewhere, in a work summary, a release certificate, an open-item entry, but the list is revised on its own slower rhythm, usually by a different person than the one who signed the work. Over a year the list becomes a description of a configuration the aircraft used to have, and the only way to see the divergence is to read it against the file that recorded each change as it happened.

What gets reviewed

  • Each equipment list entry matched to an installation record and release document in the CAMO file
  • Removals and installations from work summaries and open-item entries screened for list follow-through
  • Modification-driven equipment changes cross-checked against the modification status report
  • Serial-number-level agreement between the list, release certificates, and utilization tracking where applicable
  • Loaned, pooled, or exchanged units traced for both installation evidence and formal acceptance
  • The list's revision history examined for gaps relative to the tempo of recorded changes

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

  • Every list entry added since the prior revision has a release document, FAA Form 8130-3 or EASA Form 1 as appropriate, in the file
  • No removal recorded in the CAMO file leaves the removed unit still shown as installed
  • Serial numbers on the list agree with the serial numbers on the supporting release paperwork
  • Items introduced by modification appear on the list with the same effectivity the approval describes
  • The list revision in circulation matches the revision the source file identifies as current

Evidence normally required

  • The current aircraft equipment list and its revision history
  • CAMO status reports, work summaries, and the open-item log for the review period
  • Release certificates and installation records for changed items
  • The modification status report and related approvals
  • Any rotable pool, loan, or exchange documentation touching the aircraft

Common discrepancies

  • Units removed months earlier that persist on the list because the revision cycle never caught the removal
  • Serial numbers on the list transcribed from planning documents that differ from the serial actually installed and released
  • Modification kits shown as installed on the list while the modification status report has the change open
  • Loaned units flying on the aircraft with installation evidence but no formal entry into the operator's configuration records

What is at stake

A stale equipment list undermines whatever cites it. MEL applicability, maintenance-program effectivity, weight and balance amendments, and AD applicability assessments all reference the list as if it were current, so one wrong entry propagates into several compliance arguments simultaneously. At redelivery or sale, list-versus-records mismatches are among the first discrepancies a reviewing team raises, and each one takes hours to run down under deadline.

Move from findings to resolution

Move from findings to a documented resolution path.

How the work runs

01

Baseline the list

Take the current revision and its history as the claim to be tested.

02

Harvest change events

Extract every installation, removal, and swap the CAMO file recorded during the period.

03

Match and mark

Pair list entries with evidence, mark orphans on both sides, and verify serials against release documents.

04

Hand over the reconciliation

Deliver exceptions, the draft corrected list, and the missing-document register.

What the buyer receives

  • An entry-level exception list stating, for each discrepancy, what the file shows and what the list claims
  • A reconciled draft equipment list the CAMO can review and adopt
  • A register of missing release or installation documents with suggested recovery sources

Who uses the output

  • Continuing-airworthiness managers anchoring the configuration side of the status baseline
  • Maintenance control and MEL coordinators who apply the list operationally every day
  • Technical records staff who will issue the corrected revision and file the recovered documents

How the work fits into the transaction or program

Configuration is the meeting point of three other reviews in the source-file series: modification status establishes what was approved, weight and balance measures what the changes did, and logbook continuity fixes when they happened. The equipment list review closes the square by confirming what the aircraft carries now, which is the fact the daily operation actually runs on.

Jurisdiction-specific considerations

US-registered aircraft rely on 14 CFR 43 recordkeeping for each installation and on FAA Order 8130.21 series releases for traceability, so the review keys on 8130-3 coverage. Under EASA, Regulation 1321/2014 places configuration knowledge squarely on the CAMO, and airworthiness reviewers routinely sample the equipment list against Form 1 evidence. Mixed-history aircraft frequently carry release documents from both systems, and the review notes where dual-release forms would simplify future transfers.

Regulatory limits

Nothing in this review installs, accepts, or approves anything. It does not determine airworthiness, judge part eligibility, or issue release documentation. It reports where the equipment list and the source file agree and where they do not, leaving disposition to the operator and its authority.

What this review does not cover

  • Physical inventory or borescope-level verification of installed units
  • Parts eligibility or suspected-unapproved-parts investigation
  • Issuance of equipment list revisions under any approval holder's authority

Specific to this review

  • List drift is fastest on high-rotation commodities such as wheels, brakes, and galley inserts, and slowest on the avionics entries auditors check first, which is why self-assessments underestimate the problem.
  • A serial-number mismatch between list and release paper is more often a transcription artifact than a wrong part, but proving which takes the same document retrieval either way.
  • Pooled and loaned rotables are the classic origin of installed-but-never-received units, because the commercial paperwork and the technical records travel on separate tracks.
  • Reconciling the list immediately after a modification campaign costs a fraction of reconciling it at the next transition, when the installers who could explain discrepancies have dispersed.

Sources

Frequently asked questions

Is this the same as a physical configuration audit?

No, and the two answer different questions. A physical audit establishes what is on the aircraft today; this review establishes what the records can prove. An operator ideally wants both to agree, and running the records review first means the physical audit, if one follows, checks a short exception list instead of the whole aircraft.

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.