Configuration at handover
Equipment list and configuration records review at lease transition
An equipment list that no longer matches the aircraft is one of the fastest ways to stall an acceptance, and this review exists to catch that before the counterparty does. It compares the aircraft equipment list presented in the lease-transition file with the installation, removal, and release evidence scattered through the folders, acceptance notes, and tracker entries. Serialized items known to have been touched during the term are traced to documents such as FAA Form 8130-3 or EASA Form 1. What comes out is a line-referenced set of exceptions the transition lead can hand across the table with sources attached.
When this review is needed
- Redelivery is approaching and the counterparty has announced it will sample the equipment list against release paperwork.
- Rotable swaps and loaner installations during the term were handled under dispatch pressure and their paper trail was never consolidated.
- Two versions of the list are circulating and nobody can say with confidence which revision governs.
- The incoming operator is building its maintenance system from the handover list and wants each serialized line evidenced first.
The problem
Equipment lists drift. Rotables swap during line maintenance, modifications add and delete items, loaner units go on against an AOG clock, and each event should update the list but frequently only updates a logbook. By transition time the list is the reference the incoming operator will load into its tracking system, which converts every stale line into that operator's future problem, and they know it. Their reviewers arrive prepared to test the list hard.
What gets reviewed
- Compare the aircraft equipment list line by line with installation and removal records from the lease term
- Trace serialized items to authorized release documentation such as FAA Form 8130-3 or EASA Form 1
- Check modification and SB embodiment records for items those changes added, relocated, or deleted
- Reconcile loaner and exchange units mentioned in correspondence against what the list carries at handover
- Read acceptance notes and open-item entries for configuration questions the parties have already raised
- Flag list entries that no source anywhere in the transition folders supports
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
- Part and serial numbers on the list match the most recent installation record for each position
- Serialized items added during the term carry an authorized release document somewhere in the file
- Items removed during the term are off the list, including temporary loaners that went back to stock
- Modification records that changed equipment are reflected on the list and in its revision trail
- The revision presented at handover is the latest one the sources support, with earlier revisions retired
Evidence normally required
- The aircraft equipment list at its handover revision
- Installation and removal records, work orders, and logbook entries for the lease term
- Release certificates for serialized units installed during the term
- Modification and SB embodiment records affecting installed equipment
- Acceptance notes, correspondence, and the transition open-item tracker
Common discrepancies
- A loaner unit installed under AOG pressure still occupying the list a year after the permanent part returned
- Serialized items on the list with no release certificate in any folder
- A modification that deleted equipment the list still shows installed
- Two list revisions in circulation, with the counterparty working from the older one
What is at stake
A list accepted with silent errors propagates into the next operator's maintenance forecasting, component tracking, and parts planning, where the errors surface later as suspect units, mismatched serials, or missing release documents. Unwinding a false line after acceptance costs far more than evidencing it beforehand, and repeated list failures during sampling can push the counterparty into demanding a physical inventory that nobody scheduled.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Fix the governing revision
Establish which list revision the transition is being run against and retire the strays.
Trace the moved lines
Work through every position the term's installation and removal records touched.
Verify release documents
Match each serialized addition to its FAA Form 8130-3, EASA Form 1, or equivalent release.
Report exceptions with sources
Deliver the line-referenced exception report and draft tracker entries.
What the buyer receives
- A line-referenced exception report identifying each unsupported or contradicted entry
- A trace summary linking serialized items to their release documents
- Draft open-item entries stating the specific source needed to close each exception
Who uses the output
- Transition leads who must present a defensible configuration at acceptance
- Incoming operator engineers loading the aircraft into their maintenance system
- Asset managers tracking configuration exposure across a portfolio
How the work fits into the transaction or program
The equipment list check runs alongside the weight and balance review, since the same missed installation event usually damages both records. Downstream, the verified list anchors the delivery binder's configuration section and the incoming operator's system build. Exceptions route to the open-item tracker; entries that cannot be evidenced from the file become candidates for supplier record retrieval or a physical check.
Jurisdiction-specific considerations
On the FAA side, release documentation follows FAA Order 8130.21 procedures for Form 8130-3, while EASA-installed parts carry Form 1 under Regulation (EU) No 1321/2014, and many units in a mixed-history file hold dual releases. A registry change at transition matters here: a part released and installed acceptably under one framework may draw fresh documentation questions when the receiving authority's expectations differ.
Regulatory limits
This is a documentary comparison. It does not approve installations, does not issue or validate release certificates, and makes no determination of conformity to type design or of airworthiness. Those judgments belong to the maintenance organizations and authorities involved.
What this review does not cover
- Physical inventory or inspection of installed units
- Sourcing replacement release paperwork from shops or suppliers
- Deciding what configuration the aircraft should be redelivered in
Specific to this review
- AOG substitutions are the leading cause of list drift because paperwork priority at the moment is dispatch, and the correcting entry gets deferred past anyone's memory.
- An equipment list error rarely travels alone; the same missed event usually leaves matching gaps in the weight and balance chain and the component records.
- Incoming operators key their maintenance-system build off the handover list, so an error accepted at transition propagates directly into forecasting and parts planning.
- The list revision in the data room and the revision in the aircraft's onboard library are frequently different documents, and establishing which one governs is itself a finding.
Sources
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
Federal Aviation Administration. Completion and use of FAA Form 8130-3, Authorized Release Certificate, for new and used parts.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
U.S. Government (eCFR). Records an owner or operator must keep, including total time in service, current status of life-limited parts, and AD compliance.
Frequently asked questions
How does this differ from a physical configuration audit?
This review works entirely from documents, which means it can run remotely from the folders and well before the aircraft is available. A physical audit verifies what is bolted to the airframe; this one verifies whether the paper would support what the list claims. Many transitions need both, and the document pass tells you where the physical check should concentrate.
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.