Skip to content

Configuration diligence

Equipment list and configuration records review before an acquisition closes

Before an acquisition closes, this review tests whether the aircraft equipment list describes the aircraft the buyer is actually getting. It compares each list entry against installation records, FAA Form 8130-3 or EASA Form 1 releases, and the modification approvals that authorized the configuration. Run by records specialists for the acquisition team during diligence, it surfaces every position where the list, the paperwork, and the installed standard have drifted apart. The output is an entry-level discrepancy schedule with the evidence needed to close each line before sign-off.

When this review is needed

  • A letter of intent is signed and the technical diligence scope includes configuration records.
  • The aircraft changed operators during its life and the equipment list has been maintained in more than one system.
  • Avionics upgrades or cabin modifications were embodied under STC and the buyer needs the approvals matched to list entries.
  • The purchase agreement defines delivery condition by reference to the equipment list and someone must confirm it is accurate.

The problem

Equipment lists age badly. Rotable swaps, avionics upgrades, and cabin changes each move hardware, but the list update depends on someone closing the loop after the release certificate is filed. Over a trading life the list becomes a mixture of current entries, superseded part numbers, and installations nobody documented, and the buyer cannot see which is which from the data room copy.

What gets reviewed

  • Every equipment list entry against its installation record and authorized release certificate
  • Serial numbers on release documents against those recorded on the list
  • Modification approvals, STCs, and SBs that added, removed, or relocated equipment
  • List revision history against the maintenance entries that should have driven revisions
  • Software and part-number standards for configuration-controlled avionics

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 installed item on the list is backed by an 8130-3, EASA Form 1, or equivalent release traceable to that serial number
  • No release certificate in the file describes equipment absent from the list without a matching removal record
  • STC-installed equipment appears on the list with the approval reference that covers it
  • Part and serial numbers agree across the list, the installation entry, and the release document
  • The list revision in the data room is the latest revision the maintenance records support

Evidence normally required

  • The current aircraft equipment list with revision history
  • Installation and removal entries from logbooks or the maintenance system
  • Release certificates for installed rotables and upgraded units
  • STC and modification dossiers affecting installed equipment
  • The seller's delivery condition definition from the purchase agreement

Common discrepancies

  • Units installed years ago under an upgrade program that never reached the list
  • List entries carrying the part number of a removed unit after a swap
  • Release certificates whose serial numbers match nothing currently recorded as installed
  • STC equipment listed without the approval reference the importing authority will ask for

What is at stake

A buyer that closes against an inaccurate equipment list has bought a configuration dispute. Undocumented installations block release paperwork at the next shop visit, unmatched STC equipment complicates the next registry transfer, and the seller's warranty on the list expires with the deal. Each of those costs more to resolve without the seller at the table.

Move from findings to resolution

Move from findings to a documented resolution path.

How the work runs

01

Build the entry index

Load the current list and revision history, and assign each entry an evidence slot.

02

Match releases and installations

Pair every entry with its release certificate and installation record; log the unmatched on both sides.

03

Resolve modifications

Tie STC and SB driven changes to their approvals and confirm the list reflects the embodied standard.

04

Issue the schedule

Deliver the discrepancy schedule and evidence index in time for cure negotiation before sign-off.

What the buyer receives

  • A line-by-line discrepancy schedule keyed to equipment list entries
  • An evidence index pairing each verified entry with its release and installation record
  • Recommended closure actions sequenced against the transaction calendar
  • A short-form summary the deal team can attach to the technical acceptance file

Who uses the output

  • Acquisition leads negotiating cures or price adjustments before sign-off
  • Technical diligence engineers compiling the master findings register
  • The incoming operator's records team preparing for induction

How the work fits into the transaction or program

Configuration verification anchors several other diligence chapters: LLP traceability assumes the list is right about what is installed, and the export or registry transfer that follows closing relies on the same evidence set. Closing the list discrepancies first stops the same gaps resurfacing in three later workstreams.

Jurisdiction-specific considerations

FAA practice under 14 CFR 43 records installations through maintenance entries and release tags, while EASA registries lean on the CAMO-controlled configuration status and Form 1 chain. FAA Order 8130-21 shapes what an 8130-3 must show for the receiving side to accept it. When the aircraft crosses between systems at closing, list entries need evidence readable under both.

Regulatory limits

This is a records verification, no more. It does not inspect the aircraft, confirm physical installation, approve modifications, or issue any airworthiness finding. Whether an undocumented installation may remain in service is a question for the operator and its authority, and the review only documents the evidence position.

What this review does not cover

  • Physical audit of installed equipment against the list
  • Avionics functional testing or software load verification on the aircraft
  • Negotiation of purchase agreement configuration clauses

Specific to this review

  • Equipment list gaps cluster around fleet-wide upgrade campaigns, where paperwork was processed in batches and individual tail updates lagged.
  • A release certificate without a matching list entry is as significant as the reverse: it usually marks a swap recorded on only one side.
  • Buyers who defer list verification to induction lose the seller's obligation window and pay for closure alone.
  • Registry transfers fail late most often on STC equipment whose approval basis is valid in the exporting state but unrecognized in the importing one.

Sources

Frequently asked questions

Does this replace a physical inspection of the aircraft?

No. It establishes what the records claim and prove. A physical survey establishes what is installed. Deals need both, and discrepancies between the two usually surface first in the records review because paperwork drifts faster than hardware.

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.