Modification and STC status review inside the redelivery binder

When this review is needed

• The operator embodied cabin, avionics, or connectivity modifications during the lease and the lessor must know exactly what design standard is coming back.
• Return conditions require certain modifications removed and the de-modification work needs its own documented approval basis.
• STCs on the aircraft were issued by an authority the next registry does not automatically recognize, so validation questions are coming.
• The status report was generated from an engineering system that has never been reconciled with the embodiment records themselves.

The problem

Modification records split across three worlds: the engineering order that authorized the change, the work records that embodied it, and the certification documents that keep it legal, the STC itself, its ICA, its flight-manual supplement. Status reports are compiled from the first world and rarely verified against the other two. So a report can list a mod as embodied when the install was signed off on a different aircraft in the fleet, or as removed when half its wiring provisions remain, and nobody notices until an acceptance engineer starts opening files.

What gets reviewed

• Line-by-line verification of the modification status report against embodiment work records
• Effectivity confirmation that each claimed SB or STC applies to this serial number and was accomplished at the claimed revision
• Review of the approved-data trail for operator modifications and repairs classified as alterations
• Check that each installed STC is accompanied by its certificate, permission basis, ICA, and any AFM supplement
• Audit of de-modification claims for approval basis and completeness of removal
• Consistency check between modification status, the equipment list, and weight and balance amendments

What gets validated

• Each embodied modification traces to a work record certifying accomplishment on this airframe, at the stated revision and date
• Serial-number effectivity in the SB or STC covers the aircraft, with deviations documented through the design holder
• ICA and AFM supplements exist in the binder for every modification that requires them
• STC permission or right-to-use documentation supports continued operation under a new lessee
• Partial embodiments and provisions-only installs are described as such rather than reported as complete

Evidence normally required

• The modification status report covering SBs, STCs, and operator engineering orders
• Embodiment work packs, certification statements, and engineering-order closure records
• STC certificates, master data lists, ICA documents, and AFM supplements for installed changes
• Records of de-modifications performed or planned before return
• The equipment list and weight and balance documents for cross-checking

Common discrepancies

• A modification reported embodied fleet-wide whose work record for this particular serial number does not exist
• Installed STCs with the certificate on file but no ICA, leaving the next operator without a maintenance basis for the installation
• De-modifications that removed the equipment yet left structural or wiring provisions undocumented in any configuration record
• SB accomplishment claimed at a revision that post-dates the work, meaning the tasks actually performed differ from the tasks claimed

What is at stake

Design-standard surprises are exceptionally sticky at redelivery. A modification claimed but not evidenced blocks the incoming operator's conformity work; an STC without a transferable right-to-use or the supporting ICA leaves the next CAMO unable to maintain the installation; an incomplete de-modification puts the aircraft in a configuration no document describes. Each of these halts acceptance in a way that money alone does not fix quickly, because new engineering or new permissions take calendar time.

How the work runs

What the buyer receives

• An audited modification status with each line marked supported, partially supported, or unsupported
• A certification-document gap list covering missing STCs, ICA, permissions, and AFM supplements
• A configuration-consistency note reconciling modification claims with the equipment list and weight records

Who uses the output

• Lessor engineering managers establishing the true design standard being returned
• The incoming operator's certification and CAMO staff planning conformity and program adoption
• Operator engineering teams sequencing document retrieval and any remaining de-modification work

How the work fits into the transaction or program

Modification status connects the binder's maintenance story to its design story. Findings here propagate outward: unsupported embodiments feed the repair and alteration review where approval work is missing, configuration mismatches feed the equipment-list reconciliation, and weight-affecting changes feed the weight and balance check. Settling this report early prevents the same dispute surfacing three times under different headings.

Jurisdiction-specific considerations

Alterations on the FAA side rest on 14 CFR Part 21 approvals and Part 43 records, with AC 21-40 shaping applicant practice, while EASA changes flow through Part 21 of Regulation (EU) 748/2012. An STC issued in one system generally needs validation, or an equivalent local approval, before an operator under the other system can rely on it, and reviewers flag every installed change whose approval will not travel with the aircraft to its likely next registry.

Regulatory limits

This review verifies documentation coherence and completeness. It neither approves nor validates any modification, does not classify changes as major or minor, and does not determine conformity or airworthiness; design-approval and validation decisions belong to the certificate holders and the authorities.

What this review does not cover

• Physical conformity inspection of installed modifications
• Obtaining STC validations, permissions, or new design approvals
• Engineering assessment of modification interactions or system compatibility

Specific to this review

• Fleet-level embodiment records are a recurring trap: an SB accomplished on nine of ten aircraft produces a status report that quietly claims all ten unless someone checks tail by tail.
• An STC right-to-use rarely transfers automatically with the airframe, and discovering that at acceptance leaves the parties negotiating with a design holder who has no deadline pressure at all.
• Provisions-only installations, wiring and structure without the end equipment, sit in a documentation gray zone that only an explicit configuration statement keeps honest.
• De-modification needs approved data just as embodiment did, and returns stall when a removal was performed against nothing more than an internal engineering memo.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits