STC change planning
Certification basis impact for an approved STC change
For Certification engineer, Head of certification, and Program manager, planned design change to an approved stc raises a narrow records question: Help an STC holder classify a design change and scope its certification basis impact before committing. EE tests change significance classification, affected-area analysis, existing certification basis versus current standards against source pages and the stated requirement set, then specialists accept, reject, or qualify each AI flag. The buyer receives stc design change certification basis assessment evidence register, approval-data gap list, configuration applicability memo, with unsupported claims separated from items that need owner, holder, operator, or authority decisio
When this review is needed
- Planned design change to an approved STC 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 a change to an approved STC proceeds as an amendment or a new certificate, and whether the changed product rule (14 CFR 21.101) drags the certification basis to later amendments. The hard part is proving which summary statements are supported before the decision window closes.
What gets reviewed
- Map change significance classification using the source file and note the evidence path.
- Check affected-area analysis using the source file and note the evidence path.
- Tie existing certification basis versus current standards using the source file and note the evidence path.
- Separate reuse credit for unchanged areas using the source file and note the evidence path.
- Record EASA validation amendment questions 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 change significance classification 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 design change certification basis assessment exceptions that affect pricing, acceptance, release, or certification path.
Evidence normally required
- Change significance classification
- Affected-area analysis
- Existing certification basis versus current standards
- Reuse credit for unchanged areas
- EASA validation amendment questions
Common discrepancies
- A change called minor affects a system area tied to a later certification basis amendment.
- Unchanged-area credit is claimed without a trace to the earlier approved data.
- FAA amendment-basis logic is considered but validation authority expectations are left open.
What is at stake
Late stc design change certification basis assessment 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 Design
Confirm the exact event, affected file set, buyer role, and decision standard before any change significance classification is treated as sufficient.
Trace Certification Basis
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 Commitment Impact
Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.
Package Planning Changing
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 design change certification basis assessment evidence register
- approval-data gap list
- configuration applicability memo
- closure request list
Who uses the output
- Certification engineer use the register to decide which exceptions affect the event.
- Head of certification use the evidence map to request or close source records.
- avionics 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 a change to an approved STC proceeds as an amendment or a new certificate, and whether the changed product rule (14 CFR 21.101) drags the certification basis to later amendments. The evidence set centers on change significance classification, affected-area analysis, the delta between the existing basis and current standards, and reuse credit for unchanged areas. The likely weak points are a 'minor upgrade' reclassified as significant mid-program, substantiating to the old basis and reworking to the new one, and missing the parallel CS amendment question at EASA validation. The output gives the certification engineer a cleanup register for Certification basis impact for an approved STC change before planned design change to an approved STC.
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 design change certification basis assessment fails on evidence relationships before it fails on the headline status.
- A change called minor affects a system area tied to a later certification basis amendment 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 Design Change Certification question as the control point, so the review stays tied to Planned design change to an approved STC and the buyer decision behind it.
- The evidence starts with Change significance classification and follows Basis Assessment Commitment Impact 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 Certification engineer: 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 Approved Planning Changing Amended 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 design change certification basis assessment 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. FAA type certification process, certification basis establishment, and compliance findings.
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 design change 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 planned design change to an approved stc or can be closed later without changing the decision.
What evidence has to be available before this work starts?
The starting point is change significance classification, 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 certification engineer 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.