PMA basis

Choosing your PMA basis for identicality vs test-and-computation vs licensing agreement

For PMA suppliers, equipment suppliers, MROs, this review is used when PMA part program start. EE checks chosen basis and its rationale, for identicality the licensing agreement and identicality documentation, for test-and-computation the design data against the approval basis, the configuration baseline, and the available certification records. The output gives certification engineers and product managers an evidence map, discrepancy register, request list, and closure plan for the records that need applicant, supplier, or authority disposition.

What gets reviewed

Index chosen basis and its rationale against the claim it supports.
Compare for identicality the licensing agreement and identicality documentation against the claim it supports.
Trace for test-and-computation the design data against the claim it supports.
Challenge substantiating analyses/tests and any reverse-engineering controls against the claim it supports.
Reconcile plus the 8110/PMA compliance findings against the claim it supports.
Confirm approval basis against the claim it supports.

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

Configuration match: chosen basis and its rationale fails review if the cited record cannot be tied to the current baseline.
The review notes that evidence link: for identicality the licensing agreement and identicality documentation fails review if the cited record cannot be tied to the current baseline.
Limit carryover: for test-and-computation the design data fails review if the cited record cannot be tied to the current baseline.
Source control: substantiating analyses/tests and any reverse-engineering controls fails review if the cited record cannot be tied to the current baseline.
Closure owner: plus the 8110/PMA compliance findings fails review if the cited record cannot be tied to the current baseline.

Evidence normally required

Baseline record: chosen basis and its rationale
Test file: for identicality the licensing agreement and identicality documentation
Analysis note: for test-and-computation the design data
Manual source: substantiating analyses/tests and any reverse-engineering controls
Configuration item: plus the 8110/PMA compliance findings
Closure evidence: approval basis

Common discrepancies

Finding in records: claiming identicality without a valid agreement.
Installer issue: test-and-computation data that does not actually bound the OEM configuration.
Buyer concern: a basis choice that ignores the part's criticality. This is the basis-selection decision,.
Program risk: baseline does not match the delivered records.

How the work runs

Frame Pma Basis

Confirm the exact event, affected file set, buyer role, and decision standard before any chosen basis and its rationale is treated as sufficient.

Trace Test Computation

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 Evidence

Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.

Package Licensing Agreement

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

The review notes that evidence map for PMA Basis Identicality Test Computation
Discrepancy register for PMA Basis Identicality Test Computation
Applicability and approval basis summary
Source record request list

Who uses the output

Certification engineers use the map to brief the decision.
Product managers use the register to assign closure.
DERs use the request list to collect source records.

How the work fits into the transaction or program

Which PMA approval basis a part should use, because the evidence differs sharply by basis: identicality (licensing agreement with the type-certificate holder) needs the agreement and configuration match, while test-and-computation needs independent design data, substantiating tests, and a showing the part meets the type design without the OEM's data. The evidence set centers on the chosen basis and its rationale, for identicality the licensing agreement and identicality documentation, for test-and-computation the. The likely weak points are claiming identicality without a valid agreement, test-and-computation data that does not actually bound the OEM configuration, and a basis choice that ignores the part's criticality; This is the basis-selection decision, distinct from the artifact-by-artifact PMA data pages. The output gives the certification engineer a cleanup register for Choosing your PMA basis for identicality vs test-and-computation vs licensing agreement before PMA part program start.

Start with a single asset

Reduce finding cycles by checking the package first.

Regulatory limits

EE does not issue approvals, make compliance findings, approve manuals, or determine airworthiness. The review gives the applicant, designee, buyer, or authority-facing team a clear evidence record for their own decisions.

Specific to this review

which PMA approval basis a part should use, because the evidence differs sharply by basis: identicality (licensing agreement with the type-certificate holder) needs the agreement and configuration match, while test-and-computation needs independent design data, substantiating tests, and a showing the part meets the type design without the OEM's data.
Chosen basis and its rationale often controls whether later summaries can be trusted.
Claiming identicality without a valid agreement is treated as a record gap until an owner closes it.
FAA evidence should stay distinguishable from commercial claims and installer notes.
The scope uses the Pma Basis Identicality Test question as the control point, so the review stays tied to PMA part program start and the buyer decision behind it.
The evidence starts with Chosen basis and its rationale and follows Computation Support Certification Evidence 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 Choosing Licensing Agreement Explain questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
The handoff value comes from Evidence map for PMA Basis Identicality Test Computation; it gives the next reviewer a precise map instead of another broad request for a better file.

Sources

14 CFR Part 21 - Certification Procedures for Products and Articles

U.S. Government (eCFR). Type certificates, STCs (Subpart E), TSO authorizations (Subpart O), PMA (Subpart K), and export airworthiness approvals (Subpart L).

Order 8110.4 - Type Certification

Federal Aviation Administration. FAA type certification process, certification basis establishment, and compliance findings.

Frequently asked questions

What makes this product-types review different from a general file audit?

The scope is tied to pma basis identicality test and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block pma part program start or can be closed later without changing the decision.

What evidence has to be available before this work starts?

The starting point is chosen basis and its rationale, 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

Parts Manufacturer Approval (PMA)Approved Data Acceptable Data Designated Engineering Representative (DER)Compliance Finding (Finding of Compliance)Type Design

Pitot-static and air data computer TSO evidence for accuracy, lag, and icingPlanning pitot static air data tso? EE reviews DO-160G reports, configuration limits, and missing support, the Critical and life-limited PMA parts evidence review for the agreed certification basisBefore submittal, EE tests critical and life-limited PMA parts records against the agreed certification basis Means-of-compliance map support for a PMA article approval packageAn assigned method with no completed evidence behind it is a finding waiting to happen. We trace each PMA requ Compliance matrix support for a PMA article approval packageA compliance matrix with stale evidence references stalls FAA review of your PMA article. We surface missing r ETSO deviation and DDP package evidence review for the agreed certification basisFor ETSO deviation and DDP package, EE maps cS-ETSO index entry to the claim and flags configuration, rational

Where this fits

Service: TSO and STC Certification For PMA For Equipment

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.