Reconciling the equipment list against a component-history source file

When this review is needed

• The equipment list still shows the unit removed two shop visits ago, and a trace is about to be built on that position.
• A physical survey found a serial number on the rack that no configuration record anticipated.
• Repeated component exchanges at outstations have outpaced the configuration system's updates.
• A transaction checklist calls for an equipment list reconciled to release certificates, and the last reconciliation has no date anyone can find.

The problem

Equipment lists drift one exchange at a time. A swap done overnight at an outstation gets a logbook entry but no list update; a modification rolls a part number that the list keeps at its old dash; a data migration truncates serial numbers. Each miss is small, and together they produce a list that no longer describes the aircraft, while every downstream document keeps citing it as if it did.

What gets reviewed

• Equipment-list entries for the subject component and its position compared with the installed-part records
• Serial and part numbers on the list traced to the release certificate for the fitted unit
• Exchange history from the movement records replayed against successive list revisions
• Modification-driven part-number rolls confirmed as reflected on the current list
• List positions and quantities checked against the approved configuration basis for the aircraft
• Discrepancies classified as list errors, record gaps, or genuine unknown configuration

What gets validated

• The serial number on the list for the subject position matches the most recent installation record
• Every exchange in the movement history is reflected by a list revision or an identified update failure
• Part numbers on the list agree with post-modification numbers where changes were embodied
• Each listed unit can be tied to a release certificate somewhere in the source file
• No position shows two units documented as simultaneously installed

Evidence normally required

• The current aircraft equipment list and prior revisions covering the trace period
• Installed-part lists and component movement records from the source file
• Release certificates for units fitted to the subject position
• Modification records that changed part numbers or added equipment
• Any physical survey or inventory results available for cross-checking

Common discrepancies

• A list entry naming the unit that was removed, with the fitted unit appearing nowhere in configuration records
• Serial numbers truncated or transposed during a records-system migration
• Post-modification part numbers absent from the list years after embodiment
• Two documents each asserting a different unit in the same position on the same date

What is at stake

Configuration drift compounds: an inaccurate list feeds wrong effectivity calls for AD and SB work, misleads the next shop's planning, and hands a counterparty an easy demonstration that the operator's records cannot be taken at face value. Unwinding drift late means re-deriving the configuration from primary records under deadline, the same work this review does calmly and earlier.

How the work runs

What the buyer receives

• A reconciliation report flagging each list entry the evidence contradicts or cannot support
• A corrected configuration picture for the subject position with its evidentiary basis cited
• A classified discrepancy log separating clerical fixes from genuine configuration unknowns

Who uses the output

• Configuration control staff correcting the list from cited evidence rather than assumption
• Records leads deciding whether the component trace can rely on the list as a source
• Planning and engineering teams whose effectivity decisions consume the corrected picture

How the work fits into the transaction or program

The equipment list is both an input and an output of the wider source review: the trace uses it to locate the component, and the review's findings correct it in turn. Discrepancies established here flow into the weight and balance check, since an unrecorded exchange is often also an unrecorded mass change.

Jurisdiction-specific considerations

FAA record expectations reach the equipment list through 14 CFR 91.417 and the Part 43 entries behind each installation, with FAA Order 8130-21 shaping the release documentation that fitted units should carry. Under EASA rules the CAMO's configuration records serve the same function within Regulation 1321/2014, and cross-registry transfers frequently surface list conventions that do not translate cleanly between systems.

Regulatory limits

The review establishes documentary consistency between the list and the evidence. It does not determine whether the installed configuration is approved or airworthy, does not authorize configuration changes, and a physical inventory of the aircraft is outside its reach unless survey data is supplied.

What this review does not cover

• Physical inspection or inventory of installed equipment
• Approval of configuration changes or deviations
• Reconciliation of positions unrelated to the subject component

Specific to this review

• Outstation exchanges are the dominant drift source because the update path from a line station to the configuration system is the longest and least supervised in the operation.
• System migrations leave a signature: discrepancies clustering around a single date almost always mark a data conversion rather than dozens of separate failures.
• A list that is wrong about one heavily exchanged position is usually wrong about its neighbors, since the same crews and the same update path handled them.
• The double-installation pattern, two units documented in one position, generally means a removal record was never raised, and the missing removal is the document to chase.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits