STC holder obligations
Post-certification data and ICA obligation review for STC holders
For Quality manager, Head of certification, and Accountable manager, authority audit or pending company sale raises a narrow records question: Scope an independent review of an STC holder's continued airworthiness and data obligations. EE tests reporting process, its records, ICA revision log against source pages and the stated requirement set, then specialists accept, reject, or qualify each AI flag. The buyer receives stc holder post certification obligations evidence register, approval-data gap list, configuration applicability memo, with unsupported claims separated from items that need owner, holder, operator, or authority decisions.
When this review is needed
- Authority audit or pending company sale gives the team a fixed window for evidence review.
- A status list or package summary needs source-page testing.
- High-risk records cannot be left to sampling.
- A decision register is needed for commercial, maintenance, or certification use.
The problem
The decision is whether an STC holder is actually meeting its post-issuance obligations: occurrence reporting under 14 CFR 21.3, ICA revision service, retention of substantiating data, permission letters, and support to installers. The hard part is proving which summary statements are supported before the decision window closes.
What gets reviewed
- Map reporting process using the source file and note the evidence path.
- Check its records using the source file and note the evidence path.
- Tie ICA revision log using the source file and note the evidence path.
- Separate in-service findings using the source file and note the evidence path.
- Record design changes using the source file and note the evidence path.
Scope this review
Tell us the asset, the event, and the evidence in scope, and we will outline a focused first engagement.
Identify what is missing against the means of compliance.
What gets validated
- Accept reporting process only when a readable source page supports it.
- Reject index-only support where no underlying document can be opened.
- Hold AI classifications that lack reviewer disposition.
- Escalate stc holder post certification obligations exceptions that affect pricing, acceptance, release, or certification path.
Evidence normally required
- Reporting process
- Its records
- ICA revision log
- In-service findings
- Design changes
Common discrepancies
- Unreported in-service failures surfacing in an authority audit.
- ICA never revised after a design change.
- Certificates transferred without the records that must travel with them.
What is at stake
Late stc holder post certification obligations findings can force rework, commercial holdbacks, or delayed delivery. Unresolved items also weaken the team's position when a counterparty asks for source proof.
How the work runs
Frame STC Holder
Confirm the exact event, affected file set, buyer role, and decision standard before any reporting process is treated as sufficient.
Trace Certification Obligations
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 Obligation Audit
Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.
Package Issuance Data
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
- stc holder post certification obligations evidence register
- approval-data gap list
- configuration applicability memo
- closure request list
Who uses the output
- Quality manager use the register to decide which exceptions affect the event.
- Head of certification use the evidence map to request or close source records.
- equipment suppliers leaders use the summary to brief the next approval, release, or deal meeting.
How the work fits into the transaction or program
The decision is whether an STC holder is actually meeting its post-issuance obligations: occurrence reporting under 14 CFR 21.3, ICA revision service, retention of substantiating data, permission letters, and support to installers. The evidence set centers on the reporting process and its records, the ICA revision log versus in-service findings and design changes, data retention completeness, and certificate transfer records. The likely weak points are unreported in-service failures surfacing in an authority audit, ICA never revised after a design change, and certificates transferred without the records that must travel with them. The output gives the quality manager a cleanup register for Post-certification data and ICA obligation review for STC holders before authority audit or pending company sale.
Start with a single asset
Reduce finding cycles by checking the package first.
Regulatory limits
EE does not issue STCs, approve design data, classify changes for an authority, make compliance findings, or decide regulatory acceptance. The review organizes evidence and open questions for the applicant, holder, authorized representatives, and authorities.
What this review does not cover
- Authority application filing
- Approval of design or maintenance data
- Physical conformity inspection
- Selection of a kit or vendor
Specific to this review
- stc holder post certification obligations fails on evidence relationships before it fails on the headline status.
- Unreported in-service failures surfacing in an authority audit is handled as a decision risk.
- The strongest output is the source link, because it lets a reviewer challenge or close each line quickly.
- AI comparison is useful only after the archive has enough structure to avoid false confidence.
- The scope uses the STC Holder Post Certification question as the control point, so the review stays tied to Authority audit or pending company sale and the buyer decision behind it.
- The evidence starts with Reporting process and follows Obligations Review Obligation Audit 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 Quality 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 After Issuance Data Ica questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
- The handoff value comes from stc holder post certification obligations evidence register; it gives the next reviewer a precise map instead of another broad request for a better file.
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.
European Union / EASA. EASA design and production certification, STCs, ETSO authorizations, and EASA Form 1 release.
Frequently asked questions
What makes this workflows review different from a general file audit?
The scope is tied to stc holder post certification and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block authority audit or pending company sale or can be closed later without changing the decision.
What evidence has to be available before this work starts?
The starting point is reporting process, 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 quality 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.