Skip to content

Configuration on paper

Equipment list and configuration records checked against scanned sources

An aircraft equipment list is only as reliable as the installation evidence sitting behind each line, and after digitization that evidence is a set of image files. This review samples equipment list entries and pulls their scanned support: the FAA Form 8130-3 or EASA Form 1 releasing the unit, the installation record fitting it to this aircraft, and the modification approval where fitment came from a design change. Part and serial numbers are read from the images themselves, not from index metadata, because OCR mangles exactly those fields. Records control receives an entry-level exception register for correcting the list and the index together.

When this review is needed

  • The equipment list was regenerated from OCR or system migration and rotable serial numbers no longer inspire confidence.
  • Component release certificates were scanned in bulk and their linkage to installed positions is uncertain.
  • A lease delivery condition requires the equipment list to be supportable line by line from records.
  • Avionics or interior changes over several operators have left the list and the modification history out of step.

The problem

Configuration data dies by a thousand small errors. A serial number misread as its near-twin, a release certificate scanned into the wrong component folder, an installation record that names the position but not the part: each is trivial alone, and collectively they detach the equipment list from reality. Digitization multiplies the failure points because part numbers full of zeros, ohs, ones, and els are precisely what OCR reads worst, and the list keeps its confident formatting either way.

What gets reviewed

  • Equipment list entries sampled across ATA chapters, with rotable and serialized items weighted
  • Release documentation located for each sampled unit: 8130-3, EASA Form 1, or equivalent authorized release
  • Installation evidence found tying the unit to this aircraft and position, with date and certification
  • Part and serial numbers transcribed from the images and compared character by character with the list
  • Fitment authority checked against the modification or type design records where the item is not baseline
  • Removal records checked for sampled positions to confirm the listed unit is the last one installed

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

  • The serial number on the scanned release matches the equipment list and the installation record exactly
  • Release documents are complete scans, with block entries and the certifying signature readable
  • Installation dates precede or match the events the list attributes them to
  • No sampled position shows a later removal without a subsequent installation supporting the current entry
  • Items introduced by modification cite an approval present in the archive

Evidence normally required

  • The current aircraft equipment list export
  • The scanned component records: release certificates, installation and removal documentation
  • Modification and STC records for non-baseline equipment
  • Index or metadata exports from the digitization project
  • Any component tracking system extract, for endpoint comparison

Common discrepancies

  • Serial numbers differing between list and release by one OCR-typical character, such as 0 for O
  • A release certificate filed under a similar part number belonging to a different unit family
  • Installed positions where the archive's last document is a removal, contradicting the current list
  • Galley and interior equipment listed with no installation evidence because it arrived via an undocumented cabin change

What is at stake

An equipment list line without traceable release and installation evidence turns a routine component question into a provenance investigation. At redelivery, unsupported rotables are swap-or-substantiate items with real cost, and a pattern of them invites the counterparty to distrust the whole configuration record, expanding the audit far beyond the original lines.

Move from findings to resolution

Move from findings to a documented resolution path.

How the work runs

01

Draw the sample

Select list entries across chapters and value classes, weighting serialized rotables and modification-introduced items.

02

Assemble the evidence

Locate release, installation, and fitment-authority documents for each sampled entry in the archive.

03

Read at character level

Compare part and serial identity between images and list exactly, and test each position's document endpoint.

04

Register and correct

Issue the exception register and corrected-data file, and mark misfiled documents for re-indexing.

What the buyer receives

  • An exception register at entry level: list line, defect type, and the evidence located or missing
  • A corrected-data file for list maintenance, with each correction tied to its source image
  • A misfiling report for the archive index where documents were found under wrong references

Who uses the output

  • Records control teams correcting the equipment list and its supporting index
  • Component and supply chain staff resolving identity conflicts on installed units
  • Redelivery and diligence teams substantiating configuration line by line

How the work fits into the transaction or program

Configuration evidence connects outward in both directions: upstream to the modification records that authorize non-baseline fitment, and downstream to weight and balance amendments and LLP traceability where serialized life matters. In a staged archive review this check typically follows the modification status review, inheriting its findings about which changes should have introduced equipment.

Jurisdiction-specific considerations

Authorized release documentation follows FAA Order 8130.21 conventions for the 8130-3 and its EASA Form 1 counterpart, and dual-release forms are common on components that crossed the Atlantic. Recordkeeping obligations under 14 CFR 91.417 and Regulation 1321/2014 both extend to the current status of installed equipment, so reviewers under either regime treat an unsupported serialized item as a records gap, whichever authority released it.

Regulatory limits

Findings address documentary support only. The review does not determine the airworthiness or eligibility of any installed part, does not authenticate release certificates with issuing organizations, and does not approve the equipment list or the configuration it describes.

What this review does not cover

  • Physical inventory or borescope-style verification of installed units
  • Suspected unapproved parts investigation, beyond flagging documents that warrant one
  • Reconciliation of stores or inventory holdings not installed on the aircraft

Specific to this review

  • Character-level comparison is the core discipline here: most serial discrepancies in digitized archives are single-character OCR substitutions, which fuzzy matching hides and exact reading exposes.
  • Dual-release 8130-3 and EASA Form 1 documents cut both ways, easing cross-registry transfers while doubling the fields where scan quality can obscure a certifying block.
  • The last-document test on a position, asking whether the archive ends with an installation or a removal, catches list staleness that entry-by-entry evidence checks miss.
  • Cabin equipment is the chronic weak zone, since interior changes are often executed as bulk projects whose paperwork treats the cabin as one item rather than as serialized units.

Sources

Frequently asked questions

Does this replace a physical configuration audit?

No. It establishes what the records support, which is a different question from what is bolted to the aircraft. The two audits are complementary: paper-to-aircraft discrepancies found physically still need the records side resolved, and this review defines the records side precisely.

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.