Equipment lists
Equipment list reconciliation within the modification-baseline source file
An aircraft equipment list is only useful if it describes what is actually installed, and modifications are the main force pulling it out of date. In this review, records specialists reconcile the equipment list against the source package: modification kits that added or deleted line items, part-number supersessions driven by SBs, rotable changes recorded in maintenance data, and the release paperwork behind serialized units. It runs inside a configuration baseline effort, before the list is treated as authoritative. Deliverables center on a line-level reconciliation and an exception set formatted for the configuration support package.
When this review is needed
- Avionics or cabin modifications were embodied and the equipment list revision predates them.
- Part numbers on the list still show pre-supersession values after SB embodiment was claimed elsewhere in the file.
- Serialized units on the list lack the release certificates that would let them survive an audit.
- A lease return or sale requires an equipment list the counterparty can verify line by line.
The problem
Equipment lists are maintained on a different rhythm than the events that change them. A rotable swap happens overnight and lives in the maintenance system; a mod kit deletes two line items and adds five, and the list revision that should follow gets scheduled and rescheduled. After a few years the list is an archaeology problem: some lines describe the current aircraft, some describe a configuration two modifications ago, and nothing on the face of the list distinguishes them.
What gets reviewed
- Line-by-line comparison of the equipment list against configuration records in the source package
- Mod-kit content sheets applied to the list: additions, deletions, and part-number changes
- SB-driven supersessions checked against listed part numbers
- Serialized line items matched to release paperwork, FAA Form 8130-3 or EASA Form 1
- Rotable change history sampled against list revisions over the same period
- The list's own revision log examined for skipped or undocumented revisions
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
- Every modification claimed as embodied has its equipment-list consequence reflected, or an exception is raised
- Listed part numbers agree with the latest supersession state the source file supports
- Serial numbers on the list match the release certificate and the installation record for that position
- Deleted items from mod kits no longer appear as installed anywhere on the list
- List revisions cite the modification or maintenance event that triggered them
Evidence normally required
Common discrepancies
- Line items added by a modification kit that never made it onto any list revision
- A superseded part number still listed years after the SB that replaced it was claimed embodied
- Serialized units listed with no release certificate traceable in the package
- Ghost lines describing equipment removed by a cabin reconfiguration and never deleted
What is at stake
A stale list undermines the whole configuration story, because it is the record most easily checked against the physical aircraft. When an inspector or buyer finds a line that fails against the airplane, the natural inference is that other configuration records have decayed the same way, and the burden shifts onto every claim in the baseline.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Baseline the list
Take the current list and its revision log as the object under test, noting gaps in the revision sequence.
Apply the change history
Replay mod kits, supersessions, and rotable changes from the source package against the list, line by line.
Verify the serials
Match serialized lines to release paperwork and installation records for their positions.
Publish the reconciliation
Deliver the marked-up list, the exception set, and the revision-health note.
What the buyer receives
- A reconciled equipment list markup showing supported, stale, and unsupported lines
- An exception set naming the missing evidence or the missing revision per line
- A revision-history health note flagging periods when list maintenance lapsed
Who uses the output
- Configuration managers certifying the list as part of the baseline
- Records staff sourcing release certificates for the flagged serialized units
- Lease and transaction teams preparing for counterparty verification
How the work fits into the transaction or program
The equipment list strand closes the loop that the modification-status and weight-and-balance strands open: a verified embodiment implies list changes, and list changes imply weight changes. Exceptions raised here are cross-referenced against both neighbors so the configuration support package presents one consistent account rather than three overlapping ones.
Jurisdiction-specific considerations
Release paperwork is the main jurisdictional fork: units installed under FAA custody should trace to 8130-3 forms consistent with FAA Order 8130.21 practice, while EASA-era installations trace to Form 1 releases under Regulation 1321/2014. Dual-history aircraft carry both, and the review checks that each unit's form matches the regulatory era and location of its installation rather than accepting any release on file.
Regulatory limits
This work is a documentary reconciliation. It does not inspect the aircraft, does not approve the equipment list or any configuration, and does not certify installed equipment as conforming; unresolved lines are reported as exceptions for the responsible operator to action.
What this review does not cover
- Physical inventory or visual verification of installed units
- Issuing revised equipment-list pages
- Procurement of replacement release certificates from part suppliers
Specific to this review
- Deletions age worse than additions: teams remember to add new equipment to the list but rarely purge what a mod removed, so ghost lines accumulate.
- A release certificate that predates the unit's recorded installation by years is a quiet red flag, often meaning the certificate belongs to a different unit of the same part number.
- List revisions triggered by modifications should cite the mod reference; revisions without a cited trigger are where undocumented configuration change hides.
- The list is the configuration record counterparties physically check first during acceptance, which makes its error rate disproportionately expensive.
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 is this different from a physical configuration audit?
A physical audit compares the list to the airplane; this review compares the list to the records that should govern it. The two find different defects. Paper reconciliation catches missing release certificates and unapplied mod kits that a walk-around cannot see, and it can be done without access to the aircraft. Where a line cannot be resolved on paper, the exception set marks it as a candidate for physical verification.
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.