Asset diligence
Lessor STC consent review for lessors
This page is for lessors, Asset managers, lenders when Lessee modification consent request puts lessor stc consent review on the critical path. EE checks proposed STC package, removal and reversibility data, lease records condition 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 Lessee modification consent request starts driving schedule or commercial exposure.
- A lessor technical or contracts manager searches for what to check before approving a lessee modification request, often triggered by an AD or mandate the lessee must meet.
- The highest-risk breakpoint is: consenting without data escrow and being stranded when the holder disappears, return conditions never updated so redelivery disputes the mod, and an irreversible mod narrowing the remarketing pool.
The problem
The decision is whether a lessor consents to a lessee's proposed STC embodiment, and on what conditions. The file set covers the STC's pedigree (holder standing, approval basis, foreign validations), reversibility and removal data, effect on residual value and next-operator acceptability, and required amendments to return conditions and records obligations. Known breakpoints include consenting without data escrow and being stranded when the holder disappears, return conditions never updated so redelivery disputes the mod, and an irreversible mod narrowing the remarketing pool.
What gets reviewed
- Review the buyer decision in the brief: Help a lessor technically evaluate a lessee's STC embodiment request before granting consent.
- Trace proposed STC package to source date, revision, owner, and current configuration.
- Match effectivity for removal and reversibility data to the serial range, article version, aircraft, or fleet in scope.
- The decision is whether a lessor consents to a lessee's proposed STC embodiment, and on what conditions.
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
- Source trail: proposed STC package is tied to a dated record, stated revision, and custodian.
- Applicability: removal and reversibility data is limited to the exact serials, models, article versions, or fleet group proven by the file.
- Revision fit: drawings, reports, instructions, releases, and matrix rows are compared for mixed baselines.
- Open-item treatment: assumptions are marked for use, limitation, escalation, or replacement evidence.
Evidence normally required
- Source record set for proposed STC package
- Program file covering removal and reversibility data
- Configuration baseline with approval basis and revision index
- Open issue log tied to lease records condition
Common discrepancies
- The file set covers the STC's pedigree (holder standing, approval basis, foreign validations), reversibility and removal data, effect on residual value and next-operator.
- Known breakpoints include consenting without data escrow and being stranded when the holder disappears, return conditions never updated so redelivery disputes the mod, and an.
- Revision mismatch leaves lease records condition 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: consenting without data escrow and being stranded when the holder disappears, return conditions never updated so redelivery disputes the mod, and an irreversible mod narrowing the remarketing pool.
How the work runs
Frame Lessor STC
Confirm the exact event, affected file set, buyer role, and decision standard before any proposed stc package is treated as sufficient.
Trace Consent Review
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 Asset Diligence
Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.
Package Wants Modify
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 a lessor consents to a lessee's proposed STC embodiment, and on what conditions. The evidence set centers on the STC's pedigree (holder standing, approval basis, foreign validations), reversibility and removal data, effect on residual value and next-operator acceptability, and required amendments to return conditions and records obligations. The likely weak points are consenting without data escrow and being stranded when the holder disappears, return conditions never updated so redelivery disputes the mod, and an irreversible mod narrowing the remarketing pool. The output gives the lessor technical manager a cleanup register for Lessor STC consent review for lessors before lessee modification consent request.
Start with a single asset
Start with a single tail and expand once the workflow is proven.
Regulatory limits
For lessor stc consent review, EE reviews proposed STC package, removal and reversibility data, lease records condition 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 a lessor consents to a lessee's proposed STC embodiment, and on what conditions.
- The file set covers the STC's pedigree (holder standing, approval basis, foreign validations), reversibility and removal data, effect on residual value and.
- Known breakpoints include consenting without data escrow and being stranded when the holder disappears, return conditions never updated so redelivery disputes the.
- The scope uses the Lessor STC Embodiment Consent question as the control point, so the review stays tied to Lessee modification consent request and the buyer decision behind it.
- The evidence starts with proposed STC package and follows Review Lessors Asset Diligence 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 Lessee Wants Modify Aircraft questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
- The handoff value comes from Lessor STC consent review 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 Help a lessor technically evaluate a lessee's STC embodiment request before granting consent..
Sources
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.
U.S. Government (eCFR). Requirement to transfer maintenance records with an aircraft on sale or transfer of ownership.
Frequently asked questions
What makes this workflows review different from a general file audit?
The scope is tied to lessor stc embodiment consent and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block lessee modification consent request or can be closed later without changing the decision.
What evidence has to be available before this work starts?
The starting point is proposed stc package, 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.