US aviation part records: separate identity evidence from eligibility claims

Define the archive as documents, not approved substitutions

When describing a replacement-part archive, start with the retained records: purchase references, part and serial identifiers, release documents and linked history. Avoid turning an inventory field labeled approved into a technical conclusion. Who entered that field, what it referred to and which evidence supported it need to be known. A proposed documentation review can remain useful even when eligibility for a particular application has not been assessed.

This guide is limited to US type-certificated aviation. FAA AC 20-62E Change 1, read on 8 October 2026, states that an authorization tag does not itself approve installation. It also distinguishes a purchase-order part-number match from FAA acceptability. The document is a technical starting point for the appropriately authorized aviation reviewer, not an installation procedure or a general rule for all maintenance industries.

Complete a documentation-status matrix

These hypothetical entries concern three documentary files, not actual parts offered for sale or licensing. File P50 has purchase and marked serial reference S091, while its attached tag refers to S019. P51 has consistent serial reference S092 but no supplied historical file. P52 links consistent S093 references to documents H93 and T93; their technical sufficiency has not been assessed by the designated aviation reviewer.

The completed matrix separates identity mismatch, missing history and evidence awaiting assessment. None of its rows is marked installable. The records owner can accurately report what was found and assign the gaps without deciding whether an alternate part can replace another. File P52’s links are a starting point for review, and the mere presence of the documents does not establish their authenticity, applicability or compliance.

Preserve part identity across revised descriptions

In your proposed internal review, record the original identifier exactly alongside any corrected interpretation. A later normalized part number should not erase the supplier’s original description or the reason for the change. Keep attachment identifiers and version history with each correction. Where a serial reference disagrees, document both values and the unresolved link instead of selecting whichever one makes the spreadsheet appear consistent.

FAA’s used-part guidance describes relevant identity and historical information, including applicable time or cycle history, and tells readers to state certain unknown approvals as unknown. Do not invent a missing history from neighboring serial numbers. For this matrix, the owner therefore keeps P51’s history unresolved. Which historical information is actually required remains an application-specific question for the responsible aviation reviewer.

Make the technical reviewer’s boundary explicit

Assign document retrieval and interpretation to different named responsibilities. The records owner can locate a file and confirm which references it contains. The designated aviation reviewer assesses what that documentation means for the actual proposed application under the applicable requirements. A commercial team should not convert evidence present into technically approved because a potential evaluator wants a simplified label. Preserve the unresolved status until its authorized determination exists.

Create a review note for each claimed status that states the specific application, the decision owner, the supporting document versions and the limits of the determination. This proposed governance step prevents a narrow historical decision from becoming a broad description of every part with the same number. If the record does not show an application or responsible decision, use a descriptive document inventory rather than an eligibility label.

FAA’s AC 43-9D maintenance-record guidance emphasizes descriptions that let a reader unfamiliar with the work understand what was done, including supported references where appropriate. Its recordkeeping material has stated air-carrier exclusions, apart from the Form 8130-3 material; use the actual applicable scope. Read the editorial update dated 30 April 2026 alongside the file’s historical references. For the proposed inventory, identify what each document describes rather than treating a title such as release as a complete interpretation of its contents.

Release only the separately reviewed documentary scope

A parts documentation archive can contain proprietary technical content, customer or operator identifiers, signatures and records supplied by other organizations. Possession alone is insufficient to decide what may be disclosed. Start with inventory categories and identified gaps, then use rights review to locate the relevant agreements and authorities. Keep confidential technical attachments inside the existing authorized environment while those questions are resolved; a filename list can also reveal sensitive relationships.

For a possible introduction, describe retained document types, coverage and unresolved interpretation limits using a fictional matrix. If the business later approves a sample, identify the named recipient, purpose and fields in a separate decision. A permissioned introduction through VOID does not authorize documents, establish a part’s eligibility or approve installation. The immediate outcome is an accurate evidence description and a technical review queue, not an approved substitution list.