Embodiment evidence
Modification and STC status backed by scanned source records
A modification status report is a set of claims: this STC embodied on this date, this SB incorporated at this shop visit. This review takes sampled lines from the report and demands that the scanned archive produce the evidence behind each one, meaning the approval document, the embodiment work record with its certification, effectivity for the specific serial number, and the follow-on items such as flight manual supplements and instructions for continued airworthiness. A records specialist runs it during archive-quality work or migration, and delivers a per-modification evidence verdict the records control lead can act on.
When this review is needed
- A buyer's technical team has asked for embodiment evidence on specific modifications and the answer lives somewhere in scanned files.
- The status report was migrated between maintenance systems and its links to source documents did not come across.
- An STC-heavy aircraft, such as one with freighter conversion or avionics upgrades, is heading into a transaction.
- Records control suspects the report lists modifications inherited from a fleet template rather than from this tail's actual history.
The problem
Modification evidence is scattered by nature. The approval might be an STC certificate in one folder, the embodiment a work order scanned with a check package from years earlier, the effectivity a line in a service bulletin, and the flight manual supplement a document nobody indexed. A status report built or migrated without those anchors keeps asserting embodiment long after the archive has lost the ability to show it, and each unsupported line is a small liability waiting for the question that exposes it.
What gets reviewed
- Status report lines sampled across STCs, manufacturer SBs, and operator-originated modifications
- Approval basis located in the archive for each sampled line: STC certificate, SB revision, or approved design change
- Embodiment work records found and read for certification, date, and aircraft identity
- Effectivity verified for this serial number, including kit part numbers where the SB varies by configuration
- Follow-on documents traced: flight manual supplements, ICA, weight and balance amendments triggered by the change
- Report metadata checked against the images for date, reference, and revision transcription errors
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
- Each sampled embodied line has a work record in the archive naming this aircraft and carrying a certifying signature
- The approval document found matches the modification actually described in the work record
- Stated embodiment dates agree between the status report, the work record, and any logbook entry
- Serial-number effectivity is explicit in the approval or SB evidence, never inferred from fleet commonality
- Superseded or partially embodied items are represented as such in the report rather than shown closed
Evidence normally required
- The current modification and STC status report for the aircraft
- The scanned archive with its index or metadata export
- Logbook entries covering the claimed embodiment dates
- STC certificates, SB copies, and design change approvals as held in the archive
- Any prior modification review or diligence findings, to target known weak lines
Common discrepancies
- An STC listed as embodied where the archive holds the certificate but no work record for this tail
- SB incorporation shown complete while the scanned work order covers only part of the affected zones
- A flight manual supplement required by the modification with no scanned copy anywhere in the archive
- Effectivity claimed by fleet association for a line-number range that excludes this airframe
What is at stake
An embodied claim that the archive cannot substantiate puts the aircraft's configuration in doubt exactly where value concentrates, since modifications like winglets, interiors, and avionics packages carry price. Worse, a modification embodied without demonstrable effectivity for the serial number raises a conformity question that engineering has to resolve before an airworthiness review or export can proceed cleanly.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Select the sample
Draw lines from the status report weighted toward high-value STCs, multi-phase SBs, and migration-era entries.
Hunt the evidence
Locate approval, embodiment, effectivity, and follow-on documents in the archive for each sampled line.
Score each line
Record which evidence elements exist, which are defective, and which are absent.
Correct and escalate
Deliver report corrections for supported findings and route effectivity conflicts to engineering.
What the buyer receives
- A substantiation matrix: every sampled modification scored against approval, embodiment, effectivity, and follow-on evidence
- An exception file identifying the missing element and its last known custodian for each failed line
- Recommended corrections to the status report where the evidence contradicts it
Who uses the output
- Records control leads correcting the modification report before it circulates externally
- Engineering and CAMO staff resolving effectivity and conformity questions the review surfaces
- Asset managers defending modification value in a sale or lease negotiation
How the work fits into the transaction or program
Modification evidence feeds three neighbors: the equipment list, which must reflect what the modifications installed; the weight and balance record, which must capture their mass effects; and the export or airworthiness review file, which will cite the configuration. Running this source review ahead of those keeps a single unsupported STC from contaminating all of them at once.
Jurisdiction-specific considerations
On the FAA side, major alterations bring Form 337 and STC documentation expectations under Part 43 and Part 21, with AC 21-40 shaping how STC data is presented. Under EASA, Regulation 748/2012 governs the design approvals while 1321/2014 requires the continuing-airworthiness record to reflect embodied changes. Cross-registered histories often mix both document styles in one archive, and the review reads each item against the regime it was embodied under.
Regulatory limits
This work establishes what the archive can and cannot substantiate. It does not approve any modification, issue or validate an STC, make a conformity or airworthiness determination, or provide the engineering judgment needed to resolve an effectivity conflict it finds.
What this review does not cover
- Physical inspection to confirm a modification is actually installed on the aircraft
- Obtaining replacement approval documents from design approval holders
- Assessment of modification interactions or cumulative design effects
Specific to this review
- Embodiment records are the most commonly missing element because the work was often scanned inside a check package indexed by check number, not by modification, leaving the document present but unfindable.
- Partial embodiment is a status report's blind spot: multi-phase SBs get marked complete when phase one closes, and only the scanned work orders reveal the remaining phases.
- Operator-to-operator transfers strip flight manual supplements more often than any other modification document, since they travel with the flight operations library rather than the technical records.
- A modification embodied under a foreign authority's approval may need bilateral acceptance evidence in the file before an FAA or EASA reviewer will credit it.
Sources
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
U.S. Government (eCFR). Type certificates, STCs (Subpart E), TSO authorizations (Subpart O), PMA (Subpart K), and export airworthiness approvals (Subpart L).
Federal Aviation Administration. STC application process, certification basis, and continued airworthiness obligations of an STC holder.
European Union / EASA. EASA design and production certification, STCs, ETSO authorizations, and EASA Form 1 release.
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
Why sample instead of reviewing every modification?
Full-population review is available when a transaction demands it, but a weighted sample across document eras and modification types finds the systemic failures, such as a migration that dropped all pre-2010 links, at a fraction of the effort. The sample result then defines where full review is worth buying.
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.