Certification data
Modification approval route assessment for operators
This page is for operators, MROs, Engineering teams when Planned aircraft modification puts modification approval route assessment on the critical path. EE checks change description, major minor criteria record, available approved data 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 Planned aircraft modification starts driving schedule or commercial exposure.
- An engineering or maintenance lead searches for STC versus field approval versus minor alteration criteria while scoping a planned mod.
- The highest-risk breakpoint is: a field approval the FSDO rejects mid-project as beyond its scope, a major alteration signed off as minor and thrown out at audit, and ignoring foreign validation needs until an export blocks.
The problem
The decision is which approval route fits a planned modification before money is spent: STC, major change to the TC, field approval, or minor alteration under existing acceptable data. The file set covers the change description against major/minor criteria in 14 CFR 21.93, the aircraft's certification basis, precedent approvals for similar mods, and what approved data already exists. Known breakpoints include a field approval the FSDO rejects mid-project as beyond its scope, a major alteration signed off as minor and thrown out at audit, and ignoring foreign validation needs until an export blocks.
What gets reviewed
- Review the buyer decision in the brief: Help a team classify a planned modification and choose the correct approval route before starting the project.
- Trace change description to source date, revision, owner, and current configuration.
- Match effectivity for major minor criteria record to the serial range, article version, aircraft, or fleet in scope.
- The decision is which approval route fits a planned modification before money is spent: STC, major change to the TC, field approval, or minor alteration under existing.
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
- Record custody: change description is checked for source, date, revision, and relationship to the current program.
- Coverage boundary: major minor criteria record must state where the evidence stops applying.
- Baseline comparison: installation, test, drawing, and compliance references are sampled for mismatched revisions.
- Disposition rule: unsupported assumptions are separated from acceptable limitations.
Evidence normally required
- Source record set for change description
- Program file covering major minor criteria record
- Configuration baseline with approval basis and revision index
- Open issue log tied to available approved data
Common discrepancies
- The file set covers the change description against major/minor criteria in 14 CFR 21.
- 93, the aircraft's certification basis, precedent approvals for similar mods, and what approved data already exists.
- Revision mismatch leaves available approved data 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: a field approval the FSDO rejects mid-project as beyond its scope, a major alteration signed off as minor and thrown out at audit, and ignoring foreign validation needs until an export blocks.
How the work runs
Frame Modification Approval
Confirm the exact event, affected file set, buyer role, and decision standard before any change description is treated as sufficient.
Trace Assessment Route
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 Certification Data
Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.
Package Major Change
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
- Modification approval route assessment discrepancy register
- source map for change description
- effectivity and configuration closure list
- decision summary with limits and escalation items
How the work fits into the transaction or program
The decision is which approval route fits a planned modification before money is spent: STC, major change to the TC, field approval, or minor alteration under existing acceptable data. The evidence set centers on the change description against major/minor criteria in 14 CFR 21.93, the aircraft's certification basis, precedent approvals for similar mods, and what approved data already exists. The likely weak points are a field approval the FSDO rejects mid-project as beyond its scope, a major alteration signed off as minor and thrown out at audit, and ignoring foreign validation needs until an export blocks. The output gives the chief engineer a cleanup register for Modification approval route assessment for operators before planned aircraft modification.
Start with a single asset
Confirm requirements map to substantiating evidence.
Regulatory limits
For modification approval route assessment, EE reviews change description, major minor criteria record, available approved data 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 which approval route fits a planned modification before money is spent: STC, major change to the TC, field approval, or minor alteration.
- The file set covers the change description against major/minor criteria in 14 CFR 21.
- 93, the aircraft's certification basis, precedent approvals for similar mods, and what approved data already exists.
- Known breakpoints include a field approval the FSDO rejects mid-project as beyond its scope, a major alteration signed off as minor and thrown out at audit, and.
- The scope uses the Modification Approval Path Assessment question as the control point, so the review stays tied to Planned aircraft modification and the buyer decision behind it.
- The evidence starts with change description and follows Route Operators Certification Data 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 Chief 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 STC Major Change Field questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
- The handoff value comes from Modification approval route assessment discrepancy 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.
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
Frequently asked questions
What makes this workflows review different from a general file audit?
The scope is tied to modification approval path assessment 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 aircraft modification or can be closed later without changing the decision.
What evidence has to be available before this work starts?
The starting point is change description, 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 chief 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.