Modification and STC status behind an owner-managed aircraft file

When this review is needed

• Avionics and connectivity upgrades were installed across the ownership under several different shops.
• The modification report predates the most recent interior or cockpit project.
• An EASA-based buyer needs the validation or acceptance status of every STC on the aircraft.
• ICA inspections for installed modifications cannot be found anywhere on the current due list.

The problem

Modifications arrive on a managed aircraft project by project: an avionics upgrade one year, a cabin system the next, each handled start to finish by the shop that installed it. The status report is a snapshot somebody compiled once and nobody owned afterward. Permission letters, Form 337s, and ICA documents scatter across job files, and the report drifts a little further from the aircraft with every project.

What gets reviewed

• Modification status report reconciled against logbooks, Form 337s, and work orders
• Approval basis identified per modification: STC, amended type design, field approval, or minor-change data
• Effectivity and applicability confirmed for this serial number and configuration
• STC permission or right-to-use documentation located where the approval demands it
• ICAs from each modification traced into the maintenance program as tracked tasks
• Interactions checked where one modification alters the basis of another

What gets validated

• Each status line carries an approval reference that exists and covers this serial
• Embodiment evidence, whether a 337, release entry, or work order, is dated and signed for every listed change
• ICA requirements from installed modifications appear as tasks at the correct intervals
• Equipment or wiring evident in other records but missing from the report is identified and traced
• Removed modifications show removal records instead of lingering on the status

Evidence normally required

• The current modification and STC status report
• Form 337s from the owner's folders and the FAA registry file
• STC permission letters and ICA documents for each modification
• Work orders and release entries from the installing shops
• The current due list, for verifying ICA loading

Common discrepancies

• A connectivity system flying on the aircraft with its STC never entered on the status report
• ICA inspection tasks absent from tracking for a modification the report lists as embodied
• No right-to-use letter for an STC embodied years ago by a shop that has since closed
• A system long since removed still carried as installed

What is at stake

A modification without approval evidence casts doubt on whether the aircraft conforms to its own records. Buyers demand substantiation or removal, an EASA import can stall on an STC with no validation path, and ICAs that never reached the program mean inspections silently overdue since the day of embodiment.

How the work runs

What the buyer receives

• A reconciled modification status with the approval basis stated per line
• An exception list separating missing approvals, missing embodiment records, and missing ICAs
• A transferability note per STC where an EASA-bound sale makes it relevant

Who uses the output

• The owner representative answering configuration questions during the sale
• Completion and avionics shops quoting future work against the real configuration
• The incoming CAMO loading ICA tasks into its program

How the work fits into the transaction or program

Modification status ties the equipment-list, weight-and-balance, and program reviews together: a single modification exception typically spawns entries on at least two sibling exception lists. Reconciling the report early lets those reviews consume a corrected configuration instead of compounding the drift.

Jurisdiction-specific considerations

FAA modifications rest on STCs, field approvals, or minor-change determinations, with Form 337s marking the major alterations. EASA recognition runs through validation or acceptance arrangements per STC, and a field approval has no direct EASA equivalent at all. The likely direction of sale therefore reorders the exception list: paper that is airtight domestically can top the risk table for an export.

Regulatory limits

The review approves nothing, classifies no alteration, and determines no conformity. It reports whether claimed status is supported by approvals and records. Embodiment questions and approval decisions belong to the installer, the DER, or the authority, and the deliverables are built to feed those parties, never to replace them.

What this review does not cover

• Physical conformity inspection of installed systems
• Obtaining new STC permissions, validations, or field approvals
• Design review of the modification data itself

Specific to this review

• Field approvals are the least portable approval type, and on an export-likely aircraft they lead the exception list even when domestically unimpeachable.
• ICA loading is the check that fails most often: the shop embodies the modification and the tracking database never hears about the inspections it created.
• One records request to the registry often recovers 337s and approvals the owner's folders lost, closing several status lines in a single stroke.
• Right-to-use matters because an STC is property; embodiment without permission surfaces in the buyer's legal review rather than the technical one, and later than anyone would like.
• Removed systems left on the report are cheap to correct and expensive to ignore, because every stale line erodes confidence in the accurate ones.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits