Installed-configuration diligence
Equipment list and configuration records review in the data room
An equipment list source review tests whether the aircraft equipment list a seller posts describes hardware the data-room documents can account for. Sampled line items are traced to installation records and release certificates, and the list is reconciled with the modification status and weight and balance documents in the same room. Buy-side diligence teams commission it before the exception schedule closes. The product is a line-referenced exception list and a view of which configuration claims hold.
When this review is needed
- The equipment list was exported from the seller's system on a date long before the data room opened.
- High-value rotables on the list need release-tag confirmation because they drive delivery conditions.
- Avionics upgrades appear in the modification status while the list still shows the superseded units.
- A lease redelivery is coming and the list will become the baseline for the return condition.
The problem
Equipment lists drift. Line maintenance swaps a unit at an outstation, the system gets updated weeks later or never, and the exported list a seller uploads reflects some past state of the aircraft. The documents that would correct it, installation entries and 8130-3 or Form 1 tags, are scattered through work-order folders under dates nobody remembers, so reconciling even a sample takes deliberate effort the deal team has not budgeted.
What gets reviewed
- Sampled list lines traced to installation records and, where release requirements apply, to FAA Form 8130-3 or EASA Form 1 tags
- Part and serial numbers on the tags compared with the list and the installation entries
- The list reconciled against modification status for upgrade-driven equipment changes
- Removals checked for corresponding list updates, using work orders in the room
- Loose-equipment and delivery-item schedules compared with the list where the deal defines them
- Export date and source of the posted list established, with staleness assessed
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 sampled line's part number and serial number agree across the list, the installation record, and the release tag
- Tags in the room are legible, complete, and issued by an organization authorized for the work stated
- Units affected by claimed modifications appear on the list in their post-modification configuration
- Recent work orders reveal no swaps the posted list has yet to catch up with
- The list identifies its effective date and source system, so its currency can be judged
Evidence normally required
- The posted aircraft equipment list with its export date
- Work orders and installation records in the uploads
- Release certificates filed with component or shop folders
- Modification status and weight and balance documents for cross-reference
- The delivery-condition or redelivery-condition schedule, where drafted
Common discrepancies
- A sampled component whose release tag names a different serial number than the list
- Lists exported months before the room opened, with later swaps visible in work orders
- Release tags filed under purchase-order folders where the index gives no hint of the part inside
- Upgraded avionics recorded in the modification status while superseded units linger on the list
What is at stake
A wrong equipment list propagates: delivery conditions get drafted against phantom units, the weight and balance statement inherits errors, and the buyer's inventory at acceptance turns into a dispute about what was promised. Release tags that cannot be produced for on-condition components lower their value at the next removal, since the shop receiving them starts from undocumented history.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Date the list
Establish when and from what system the posted equipment list was exported.
Trace the sample
Follow selected lines to installation records and release tags, matching part and serial numbers.
Reconcile the neighbors
Check the list against modification status, weight and balance, and recent work orders for drift.
Deliver line exceptions
Issue exceptions by list line with folder references and proposed acceptance-condition language.
What the buyer receives
- A line-referenced exception list mapped to data-room locations
- A sample summary stating which configuration claims held and which failed
- Draft delivery-condition language for the lines that need tag production at acceptance
Who uses the output
- Transaction teams drafting acceptance and delivery conditions
- Records staff preparing the component-tag binder for closing
- The buyer's engineering group seeding its configuration database
How the work fits into the transaction or program
The equipment list check is the hardware half of the configuration story, with the modification review as the approval half and the weight and balance review as the consequence. It also front-loads the tag hunt that otherwise happens in closing week, when missing releases have the least time to be recovered.
Jurisdiction-specific considerations
Regimes differ on release documentation: FAA Form 8130-3 under FAA Order 8130.21 conventions, EASA Form 1 under Part-145, and dual releases where shops hold both approvals. A component that moved through both systems may carry either form legitimately, so each tag is judged against the regime of the issuing organization rather than the aircraft's current registry.
Regulatory limits
This is a documentary reconciliation. It does not certify installed configuration, approve parts or their installation, verify physical presence of equipment on the aircraft, or make eligibility determinations that belong to certificating authorities and installers.
What this review does not cover
- Physical inventory or inspection of installed units
- Sourcing replacement release tags from shops or suppliers
- Avionics capability or interoperability assessment
Specific to this review
- Tag hunts fail on filing before they fail on existence: releases usually exist somewhere, but rooms file them by purchase order or shop visit, invisible to a part-number search.
- The export date of an equipment list is its most important field and the one most often missing from the posted PDF.
- On-condition rotables without traceable release history lose shop-loop value even when installed and serviceable, which is why lessors chase tags harder than any other single document.
- A list reconciled during diligence becomes the redelivery baseline later, so exceptions closed now are disputes avoided at lease end.
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
Can missing release tags be fixed after closing?
Sometimes, at cost and slowly. Shops retain copies and can reissue, but retrieval depends on the shop still existing and cooperating once the seller has no stake. Tags requested through Q&A while the deal is open arrive far more reliably, which is the argument for running this review early.
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.