Configuration at closeout
Equipment list and configuration records in the shop-visit source file
At shop-visit closeout the equipment list should describe what is physically installed, yet the visit itself is where installed equipment changes most. This review compares the list line by line with the release certificates, work orders, and modification records in the source file. It is performed for the quality manager or the accepting lessor before the work package is signed. What comes back is a set of equipment-list entries the source records contradict, each tied to the document that shows the true configuration.
When this review is needed
- Rotable units were swapped during the visit and the list still shows the removed serial numbers.
- An STC or SB installation added equipment the list has never carried.
- The accepting operator loads configuration data from the list and needs it to match the release certificates.
- A pre-lease inspection is imminent and the configuration record must survive line-by-line scrutiny.
The problem
Shops change units to keep the visit on schedule, and each change is properly documented on its own work order and release certificate. The equipment list is downstream of all of it and usually gets updated last, from memory or from an incomplete pull of the cards. Whoever accepts the package cannot see the mismatch by reading the list alone; it only appears when the list is put against the release documents one line at a time, which nobody has hours for at closeout.
What gets reviewed
- Each equipment-list line checked against the release certificate for the installed unit
- Removals and installations on work orders reconciled to list additions and deletions
- STC and SB installations verified as present on the list with correct nomenclature
- Part and serial numbers on the list compared with FAA Form 8130-3 or EASA Form 1 data
- Loose equipment and shelf items separated from installed configuration
- Software and modification status entries checked where the list carries them
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
- No list entry shows a serial number that a work order records as removed during the visit
- Every unit installed under a release certificate in the file appears on the list
- Part numbers on the list match the release documents rather than an earlier dash number
- Modification-driven equipment changes carry the SB or STC reference on the list
- The list revision date postdates the final installation task in the source file
Evidence normally required
Common discrepancies
- Serial numbers on the list belonging to units the shop removed and shipped
- Installed units with valid release certificates that never reached the list
- A part number rolled by an SB while the list still shows the pre-mod number
- List entries copied forward from a sister aircraft's template
What is at stake
A wrong equipment list propagates into the operator's configuration control, part ordering, and the next records audit. Serial-number mismatches discovered later look like missing traceability even when the installation itself was clean, and clearing them means recalling shop records that are no longer at hand. At redelivery the list becomes a contractual document, and every stale line turns into a negotiation item.
How the work runs
Index the installs and removals
Extract every removal and installation event from the work orders and pair each install with its release certificate.
Walk the list
Take the equipment list line by line and test each entry against the paired evidence.
Classify exceptions
Separate stale entries, missing entries, and unsupported entries, since each has a different fix.
Feed the closeout revision
Hand the shop the corrections so the final list revision matches the file that supports it.
What the buyer receives
- A line-item exception report keyed to the equipment-list revision under review
- The evidencing release certificate or work order reference for every exception
- A corrected-configuration proposal the shop can adopt into the closeout revision
- A short acceptance note summarizing residual risk for the signing manager
Who uses the output
- Quality leadership accepting the work package on behalf of the operator
- Configuration and records staff who publish the next list revision
- Asset managers protecting the configuration record ahead of a lease event
How the work fits into the transaction or program
Configuration errors are cheapest to fix while the source documents and the aircraft are still in the same building. This check runs as part of closeout acceptance, feeding corrections into the final list revision that leaves with the aircraft, and it hands the operator a configuration record their own system can ingest without cleanup.
Start with a single asset
Confirm release certificates and component traceability are complete.
Jurisdiction-specific considerations
FAA practice ties installed-part legitimacy to FAA Form 8130-3 and the work-order trail under 14 CFR 43, while EASA Form 1 serves the equivalent role under EU 1321/2014. Cross-bilateral visits often leave a file with both forms covering different units, and the review keeps each list line matched to the release form its regulator expects.
Regulatory limits
The review reports documentary mismatches between the list and the source records. It does not approve parts for installation, judge the eligibility of a unit for the aircraft, or make any airworthiness determination; it tells the accepting manager where the paper disagrees with itself.
What this review does not cover
- Physical inventory or on-aircraft verification of installed units
- Part eligibility or interchangeability engineering decisions
- Maintenance of the operator's configuration database after handover
Specific to this review
- Most equipment-list errors at closeout are timing errors: the list was revised mid-visit and the last week of swaps never made it in.
- Templated lists are a known failure mode; entries copied from another tail show up as serial numbers that never had a release certificate in this file.
- A list line without a matching release certificate is ambiguous, since either the list is wrong or a document is missing, and the exception report states which reading the file supports.
- SB-driven part number rolls are easy to miss because the physical unit may not change even though the list entry must.
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
The shop says the list will be updated after delivery. Is that acceptable?
It is common, and it is exactly when errors set in. Accepting the package with a dated list is a business decision, but the exception report should exist first, because after delivery the source documents disperse and the corrections get harder to evidence.
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.