Asset diligence
Review of installed STC portfolio review for lessors for lessors
This page is for lessors, Asset managers, lenders when Lease transition or asset acquisition puts installed stc portfolio review for lessors on the critical path. EE checks installed STC inventory, validation status per mod, ICA and AFM supplement set against the approval basis, configuration baseline, effectivity, revision status, and source records named in the brief. The buyer receives a discrepancy register, evidence map, and closure request list for the next review gate. The work tests records and certification-data traceability only; it does not replace authority, delegate, approval-holder, or authorized-person decisions.
When this review is needed
- Use this review when Lease transition or asset acquisition starts driving schedule or commercial exposure.
- A lessor technical manager searches for how installed STCs affect redelivery and registry transfer after finding aftermarket mods on an asset.
- The highest-risk breakpoint is: an FAA-only STC blocking transition to an EASA operator, an orphaned STC with no ICA revision service depressing remarketing value, and missing permission letters surfacing in the next operator's induction.
The problem
The decision is whether each STC installed on an asset is properly approved, documented, and transferable to the next operator and registry. The file set covers STC certificates and holder standing, installation records, AFM supplements, ICA incorporation, and FAA/EASA validation or acceptance status per mod. Known breakpoints include an FAA-only STC blocking transition to an EASA operator, an orphaned STC with no ICA revision service depressing remarketing value, and missing permission letters surfacing in the next operator's induction.
What gets reviewed
- Review the buyer decision in the brief: Scope a certification-focused review of the installed STC portfolio on a leased aircraft.
- Trace installed STC inventory to source date, revision, owner, and current configuration.
- Match effectivity for validation status per mod to the serial range, article version, aircraft, or fleet in scope.
- The decision is whether each STC installed on an asset is properly approved, documented, and transferable to the next operator and registry.
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
- Document control: installed STC inventory has an identified owner and no uncontrolled copies carrying the main claim.
- Effectivity test: validation status per mod is rejected when coverage is inferred from similar hardware or aircraft.
- Configuration test: certificate scope, report setup, and delivered baseline are reconciled before credit is assigned.
- Exception handling: each unresolved point receives a closure owner and a target source record.
Evidence normally required
- Source record set for installed STC inventory
- Program file covering validation status per mod
- Configuration baseline with approval basis and revision index
- Open issue log tied to ICA and AFM supplement set
Common discrepancies
- The file set covers STC certificates and holder standing, installation records, AFM supplements, ICA incorporation, and FAA/EASA validation or acceptance status per mod.
- Known breakpoints include an FAA-only STC blocking transition to an EASA operator, an orphaned STC with no ICA revision service depressing remarketing value, and missing permission.
- Revision mismatch leaves ICA and AFM supplement set separated from the certificate, matrix, instruction, or delivered baseline.
- Storage completeness is higher than decision readiness because the file lacks a clear disposition for this buying stage.
What is at stake
Specific exposure for this page: an FAA-only STC blocking transition to an EASA operator, an orphaned STC with no ICA revision service depressing remarketing value, and missing permission letters surfacing in the next operator's induction.
How the work runs
Frame Installed STC
Confirm the exact event, affected file set, buyer role, and decision standard before any installed stc inventory is treated as sufficient.
Trace Review Lessors
Walk the named evidence from index entry to source artifact and mark where the trail supports, conflicts with, or fails to answer the page-specific question.
Sort Diligence Lessor
Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.
Package Delivery Redelivery
Deliver the exception list, evidence map, and owner sequence in a form that can move directly into remediation, submittal cleanup, or transaction negotiation.
What the buyer receives
How the work fits into the transaction or program
The decision is whether each STC installed on an asset is properly approved, documented, and transferable to the next operator and registry. The evidence set centers on STC certificates and holder standing, installation records, AFM supplements, ICA incorporation, and FAA/EASA validation or acceptance status per mod. The likely weak points are an FAA-only STC blocking transition to an EASA operator, an orphaned STC with no ICA revision service depressing remarketing value, and missing permission letters surfacing in the next operator's induction. The output gives the lessor technical manager a cleanup register for Review of installed STC portfolio review for lessors for lessors before lease transition or asset acquisition.
Start with a single asset
Start with a single tail and expand once the workflow is proven.
Regulatory limits
For review of installed stc portfolio review for lessors, EE reviews installed STC inventory, validation status per mod, ICA and AFM supplement set for completeness, consistency, and traceability. The work does not issue approvals, approve data, grant relief, validate STCs, accept release certificates, or make airworthiness determinations. Final decisions remain with the responsible authority, delegate, approval holder, operator, or authorized person.
Specific to this review
- The decision is whether each STC installed on an asset is properly approved, documented, and transferable to the next operator and registry.
- The file set covers STC certificates and holder standing, installation records, AFM supplements, ICA incorporation, and FAA/EASA validation or acceptance.
- Known breakpoints include an FAA-only STC blocking transition to an EASA operator, an orphaned STC with no ICA revision service depressing remarketing value, and.
- The scope uses the Installed STC Portfolio Review question as the control point, so the review stays tied to Lease transition or asset acquisition and the buyer decision behind it.
- The evidence starts with installed STC inventory and follows Lessors Asset Diligence Lessor references until every exception has a source location and a reason code.
- The finding logic separates missing paperwork, conflicting status, stale revision data, and unsupported disposition because each class closes through a different owner.
- The timing matters for Lessor technical manager: the output is useful only if the unresolved items are visible before acceptance, submittal, handback, or negotiation pressure fixes the sequence.
- The boundary control keeps Every Delivery Redelivery Transferability questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
- The handoff value comes from Review of installed STC portfolio review for lessors discrepancy register; it gives the next reviewer a precise map instead of another broad request for a better file.
- The source discipline is stricter on this page than on a general audit because the claim being tested is Scope a certification-focused review of the installed STC portfolio on a leased aircraft..
Sources
U.S. Government (eCFR). Type certificates, STCs (Subpart E), TSO authorizations (Subpart O), PMA (Subpart K), and export airworthiness approvals (Subpart L).
European Union / EASA. EASA design and production certification, STCs, ETSO authorizations, and EASA Form 1 release.
Federal Aviation Administration. STC application process, certification basis, and continued airworthiness obligations of an STC holder.
Frequently asked questions
What makes this workflows review different from a general file audit?
The scope is tied to installed stc portfolio review and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block lease transition or asset acquisition or can be closed later without changing the decision.
What evidence has to be available before this work starts?
The starting point is installed stc inventory, the current status source, and any index or matrix that tells reviewers where the supporting artifact should live. Missing inputs are logged as findings rather than filled with assumptions.
Who decides whether an open item is acceptable?
The review explains what the evidence supports and gives lessor technical manager a closure path. Acceptance remains with the buyer, operator, authority, delegated engineer, or authorized person responsible for the underlying airworthiness or certification decision.
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.