Certification data
AFM supplement stack review for operators
This page is for operators, CAMOs, owners when Authority review or pre-buy flags flight manual gaps puts afm supplement stack review on the critical path. EE checks supplement index, installed modification list, limitation conflict notes 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 Authority review or pre-buy flags flight manual gaps starts driving schedule or commercial exposure.
- An operator, owner, or CAMO searches for AFM supplement management after a review flags inconsistent or missing flight manual supplements.
- The highest-risk breakpoint is: two supplements imposing contradictory limitations on the same system, crews flying to a superseded supplement, and a missing supplement for an installed mod discovered at an authority review or pre-buy.
The problem
The decision is whether the aircraft's accumulated AFM supplements are current, consistent, and conflict-free. The file set covers the supplement list versus installed mods, revision levels versus what each holder has issued, limitations that contradict each other across supplements, and superseded or withdrawn supplements still filed as active. Known breakpoints include two supplements imposing contradictory limitations on the same system, crews flying to a superseded supplement, and a missing supplement for an installed mod discovered at an authority review or pre-buy.
What gets reviewed
- Review the buyer decision in the brief: Scope a review that reconciles the AFM supplement stack against installed modifications and current revisions.
- Trace supplement index to source date, revision, owner, and current configuration.
- Match effectivity for installed modification list to the serial range, article version, aircraft, or fleet in scope.
- The decision is whether the aircraft's accumulated AFM supplements are current, consistent, and conflict-free.
What gets validated
- Document control: supplement index has an identified owner and no uncontrolled copies carrying the main claim.
- Effectivity test: installed modification list 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 supplement index
- Program file covering installed modification list
- Configuration baseline with approval basis and revision index
- Open issue log tied to limitation conflict notes
Common discrepancies
- The file set covers the supplement list versus installed mods, revision levels versus what each holder has issued, limitations that contradict each other across.
- Known breakpoints include two supplements imposing contradictory limitations on the same system, crews flying to a superseded supplement, and a missing supplement for an installed.
- Revision mismatch leaves limitation conflict notes 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: two supplements imposing contradictory limitations on the same system, crews flying to a superseded supplement, and a missing supplement for an installed mod discovered at an authority review or pre-buy.
Move from findings to resolution
Identify the missing data behind the finding.
How the work runs
Frame Afm Supplement
Confirm the exact event, affected file set, buyer role, and decision standard before any supplement index is treated as sufficient.
Trace Review Operators
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 Data Untangling
Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.
Package After Years
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
- AFM supplement stack review discrepancy register
- source map for supplement index
- effectivity and configuration closure list
- decision summary with limits and escalation items
How the work fits into the transaction or program
The decision is whether the aircraft's accumulated AFM supplements are current, consistent, and conflict-free. The evidence set centers on the supplement list versus installed mods, revision levels versus what each holder has issued, limitations that contradict each other across supplements, and superseded or withdrawn supplements still filed as active. The likely weak points are two supplements imposing contradictory limitations on the same system, crews flying to a superseded supplement, and a missing supplement for an installed mod discovered at an authority review or pre-buy. The output gives the CAMO engineer a cleanup register for AFM supplement stack review for operators before authority review or pre-buy flags flight manual gaps.
Start with a single asset
Confirm each requirement maps to substantiating evidence.
Regulatory limits
For afm supplement stack review, EE reviews supplement index, installed modification list, limitation conflict notes 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 the aircraft's accumulated AFM supplements are current, consistent, and conflict-free.
- The file set covers the supplement list versus installed mods, revision levels versus what each holder has issued, limitations that contradict each other.
- Known breakpoints include two supplements imposing contradictory limitations on the same system, crews flying to a superseded supplement, and a missing supplement.
- The scope uses the Afm Supplement Stack Review question as the control point, so the review stays tied to Authority review or pre-buy flags flight manual gaps and the buyer decision behind it.
- The evidence starts with supplement index and follows Operators Certification Data Untangling 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 CAMO 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 Supplements After Years Modifications questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
- The handoff value comes from AFM supplement stack 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 Scope a review that reconciles the AFM supplement stack against installed modifications and current revisions..
Sources
Federal Aviation Administration. STC application process, certification basis, and continued airworthiness obligations of an STC holder.
U.S. Government (eCFR). Records an owner or operator must keep, including total time in service, current status of life-limited parts, and AD compliance.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
What makes this workflows review different from a general file audit?
The scope is tied to afm supplement stack 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 authority review or pre-buy flags flight manual gaps or can be closed later without changing the decision.
What evidence has to be available before this work starts?
The starting point is supplement index, 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 camo 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.