How detailed should genealogy records be for safety-critical aerospace components?

Genealogy records for safety-critical aerospace components should be detailed enough to reconstruct what was built, from what material, by which approved process, under which configuration, with which inspection and test evidence, and how the component relates to higher-level assemblies. There is no universal field list that fits every aerospace program. The required depth is usually driven by the drawing, specification, customer contract, design authority requirements, AS9100-based quality system controls, regulatory obligations, and the organization’s own risk assessment.

For safety-critical parts, genealogy is normally expected to go beyond basic lot traceability. A record that only says “part number, work order, and completion date” is usually not enough where failure could affect flight safety, mission capability, or continued airworthiness.

Commonly expected genealogy detail

The exact records vary, but safety-critical aerospace genealogy commonly includes:

• Part number, serial number or lot number, revision level, and configuration status at the time of manufacture.
• Raw material identity, heat, batch, certificate references, supplier identity, and receiving inspection disposition.
• Parent-child relationships between components, subassemblies, kits, and final assemblies.
• Routing steps performed, including operation sequence, timestamps, completion status, and approved work instruction or planning revision.
• Operator, inspector, and approver identities where required by procedure or contract.
• Machine, tool, fixture, gage, program, and calibration status where these affect product conformity.
• Special process records such as heat treat, coating, welding, bonding, chemical processing, NDT, or sterilization-equivalent controlled processes where applicable.
• Inspection and test results, not only pass/fail status, when characteristics are critical, key, or contractually reportable.
• Nonconformances, MRB decisions, concessions, deviations, repairs, rework, and associated approvals.
• FAI references, characteristic-level evidence, and links to ballooned drawings or AS9102 records where required.
• Environmental or handling controls when they are part of the qualified process, such as shelf life, cure time, humidity, ESD, FOD, or contamination controls.

Serial-level versus lot-level traceability

Safety-critical components often require serial-level genealogy, especially when individual part history matters for investigation, removal, life tracking, or continued airworthiness. Lot-level traceability may be acceptable for some materials, consumables, or standard parts, but only if the applicable requirements allow it and the risk is understood.

The practical test is whether the organization can isolate affected product without over-recalling or under-containing. If a heat lot, process batch, tool condition, software revision, or inspection escape is later questioned, the genealogy should support a defensible containment boundary.

Where records often fail

Genealogy programs usually fail less because a system cannot store data and more because the data model, process discipline, and integrations are incomplete. Common weak points include missing parent-child links, manual spreadsheet side records, unclear serial versus lot rules, uncontrolled rework paths, incomplete special process evidence, and disconnected supplier records.

Brownfield environments make this harder. MES, ERP, PLM, QMS, maintenance, calibration, and supplier portals often hold different pieces of the genealogy. Full replacement is usually unrealistic in aerospace-grade operations because of qualification burden, validation cost, downtime risk, integration complexity, traceability obligations, change control, and long equipment lifecycles. In practice, many sites improve genealogy by defining the authoritative source for each record type and integrating systems where the risk justifies it.

Do not collect detail without control

More detail is not automatically better. Excessive data capture can slow production, increase operator workarounds, and create records that are difficult to review or defend. The right level of detail is the level that is required, controlled, reviewed, retained, and usable during containment, audit, investigation, or customer review.

For safety-critical aerospace components, the safer assumption is that genealogy must be characteristic-aware, configuration-controlled, and linked across material, process, inspection, and assembly history. The exact implementation should be defined under change control, validated where required, and tested against realistic scenarios such as supplier escape, special process failure, tooling error, software revision issue, or field return investigation.