Modification and STC status review in the lease-transition records file

When this review is needed

• The receiving operator is building its program and manuals around a configuration the report asserts and the folders only partly support.
• A registry change is planned and someone must establish which embodied STCs would even travel with it.
• The SB status and the modification report disagree about a change the aircraft visibly carries.
• Cabin or avionics work done under a prior operator has no supplement or ICA anywhere in the delivered set.

The problem

The modification status report is typically carried forward from operator to operator, retyped and trusted, while the evidence stays wherever the work was done. Embodiments performed early in the aircraft's life sit three custodians away from the current file. By transition, the report describes a configuration everyone believes and the folders can only partially prove.

What gets reviewed

• The modification status report reconciled against SB status, STC certificates, and embodiment records
• Effectivity of each cited approval confirmed for this serial number and its configuration at embodiment
• Accomplishment records located for each embodied modification, including work orders and sign-offs
• Flight manual supplements and ICA obligations from modifications traced into the delivered manuals and program
• Interfaces between modifications checked where one change alters the effectivity of another
• Modification queries on the open-item tracker merged into a single exception baseline

What gets validated

• Each embodied entry has an accomplishment record naming the aircraft, the data revision, and the certifying release
• STC references correspond to certificates whose approved model list includes this aircraft
• The SB status and the modification report agree wherever a modification implements an SB
• Required flight manual supplements for embodied changes are present at the current revision
• ICA generated by modifications appear in the maintenance program the aircraft transitions with

Evidence normally required

• The modification status report as delivered for the transition
• STC certificates, approved model lists, and SB status reports in the file
• Embodiment work orders, releases, and check packages for claimed changes
• The delivered flight manual, its supplements, and the maintenance program document
• Open-item tracker entries and acceptance notes touching configuration

Common discrepancies

• An STC shown embodied with no work record and no supplement anywhere in the delivered file
• A modification accomplished under data whose approved model list never included this serial number
• Partial embodiments recorded as complete, with the follow-on phase quietly dropped at an operator change
• ICA from an avionics modification missing from the program the aircraft transitions with

What is at stake

An embodied modification without evidence puts the aircraft's certified configuration in question, which reaches beyond records into what the receiving operator may legally operate. Missing flight manual supplements and ICA block the receiving program from carrying the modification correctly, generating findings on their side of the transition. Configuration exceptions also persist: unresolved at this handover, they resurface enlarged at the next one.

How the work runs

What the buyer receives

• A verified modification baseline separating proven, partially proven, and unproven entries
• An exception list naming the missing element for each entry: record, effectivity, or data
• A recovery plan pointing at installers, prior operators, and certificate holders as appropriate

Who uses the output

• Transition leads sequencing configuration queries ahead of any registry work
• Receiving CAMO staff building the program and manual set for the incoming configuration
• Asset managers tracking which modifications add or subtract value, with proof attached

How the work fits into the transaction or program

The modification strand completes the configuration picture that the release-document and shop-visit reviews begin. Its verified baseline feeds the receiving operator's program build and manual set, and its exceptions join the tracker with effectivity questions flagged for early engineering attention, since those resolve slowest.

Jurisdiction-specific considerations

STC and modification approvals are jurisdiction-bound: an FAA STC issued under 14 CFR 21 does not automatically apply to an EASA-registered aircraft, and validation history matters whenever the transition changes registry. Guidance such as FAA AC 21-40 shapes what an STC application package contains, while EASA-side changes trace to Part-21 approvals under Regulation (EU) 748/2012. The review flags every embodied change whose approval basis would not travel with a registry change.

Regulatory limits

No approval, validation, or acceptance of any modification flows from this review, and no airworthiness determination is made. The review states what the file evidences about the configuration; what may be operated, and under which approvals, remains with the operator and the authority.

What this review does not cover

• Physical configuration survey of the aircraft
• Validation or transfer of STC approvals between registries
• Engineering assessment of modification compatibility

Specific to this review

• Mid-term operator changes are where partial embodiments become invisible: the second phase belonged to a planning system that did not transfer.
• Certificate holders can reissue an STC's data, and installers hold the work records; the embodiment record itself only ever existed at the installing operator, which sets the recovery order.
• Removal of a modification needs as much evidence as installation, and removals are the entries most often missing from status reports.
• Effectivity disputes are cheap to settle with the approved model list in hand and expensive to settle any other way.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits