Certification data
Obsolete part approval route assessment for pma suppliers
This page is for PMA suppliers, equipment suppliers, operators when OEM part discontinued or unsupported puts obsolete part approval route assessment on the critical path. EE checks part criticality note, available design data, approval route comparison 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 OEM part discontinued or unsupported starts driving schedule or commercial exposure.
- A supplier or operator engineer searches for PMA versus STC for a replacement part after an OEM discontinues support.
- The highest-risk breakpoint is: pursuing PMA identicality without data rights, choosing an STC where a PMA would do at a fraction of the cost, and a grounded fleet while the approval path restarts from scratch.
The problem
The decision is which approval route replaces an unavailable OEM part: PMA (identicality or test-based), an STC when the replacement changes the type design, a DER-approved repair, or an owner-produced part. The file set covers part criticality and available design data, data rights for identicality claims, the install base that amortizes approval cost, and licensing options. Known breakpoints include pursuing PMA identicality without data rights, choosing an STC where a PMA would do at a fraction of the cost, and a grounded fleet while the approval path restarts from scratch.
What gets reviewed
- Review the buyer decision in the brief: Help a supplier or operator choose the right approval route for an obsolete-part replacement.
- Trace part criticality note to source date, revision, owner, and current configuration.
- Match effectivity for available design data to the serial range, article version, aircraft, or fleet in scope.
- The decision is which approval route replaces an unavailable OEM part: PMA (identicality or test-based), an STC when the replacement changes the type design, a.
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
- Source status: part criticality note must be current enough for the cited approval basis or records event.
- Range check: available design data is mapped to the affected aircraft, article, model, or fleet segment.
- Package consistency: certificate, matrix, instruction, report, and release references are checked as a set.
- Escalation rule: missing rationale is logged as a finding rather than carried as silent credit.
Evidence normally required
- Source record set for part criticality note
- Program file covering available design data
- Configuration baseline with approval basis and revision index
- Open issue log tied to approval route comparison
Common discrepancies
- The file set covers part criticality and available design data, data rights for identicality claims, the install base that amortizes approval cost, and licensing options.
- Known breakpoints include pursuing PMA identicality without data rights, choosing an STC where a PMA would do at a fraction of the cost, and a grounded fleet while the approval.
- Revision mismatch leaves approval route comparison 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: pursuing PMA identicality without data rights, choosing an STC where a PMA would do at a fraction of the cost, and a grounded fleet while the approval path restarts from scratch.
How the work runs
Frame Obsolete Part
Confirm the exact event, affected file set, buyer role, and decision standard before any part criticality note is treated as sufficient.
Trace Approval Path
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 Assessment Pma
Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.
Package Certification 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
- Obsolete part approval route assessment discrepancy register
- source map for part criticality note
- 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 replaces an unavailable OEM part: PMA (identicality or test-based), an STC when the replacement changes the type design, a DER-approved repair, or an owner-produced part. The evidence set centers on part criticality and available design data, data rights for identicality claims, the install base that amortizes approval cost, and licensing options. The likely weak points are pursuing PMA identicality without data rights, choosing an STC where a PMA would do at a fraction of the cost, and a grounded fleet while the approval path restarts from scratch. The output gives the engineering manager a cleanup register for Obsolete part approval route assessment for pma suppliers before OEM part discontinued or unsupported.
Start with a single asset
Reduce finding cycles by checking the package first.
Regulatory limits
For obsolete part approval route assessment, EE reviews part criticality note, available design data, approval route comparison 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 replaces an unavailable OEM part: PMA (identicality or test-based), an STC when the replacement changes the type.
- The file set covers part criticality and available design data, data rights for identicality claims, the install base that amortizes approval cost, and.
- Known breakpoints include pursuing PMA identicality without data rights, choosing an STC where a PMA would do at a fraction of the cost, and a grounded fleet while.
- The scope uses the Obsolete Part Replacement Approval question as the control point, so the review stays tied to OEM part discontinued or unsupported and the buyer decision behind it.
- The evidence starts with part criticality note and follows Path Route Assessment Pma 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 Engineering 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 Suppliers Certification Data Longer questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
- The handoff value comes from Obsolete part approval route assessment 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 supplier or operator choose the right approval route for an obsolete-part replacement..
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.
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 obsolete part replacement approval and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block oem part discontinued or unsupported or can be closed later without changing the decision.
What evidence has to be available before this work starts?
The starting point is part criticality note, 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 engineering 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.