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
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
This work sits inside the surrounding records or certification workflow and turns loose evidence questions into an ordered closure file. The page-specific framing is 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 review notes that evidence reviewed: the chosen basis and its rationale, for identicality the licensing agreement and identicality documentation, for test-and-computation the. For pma basis identicality test, the practical output is a defensible record of what was checked, what did not match, who owns the fix, and which issue remains outside the review boundary. The pma basis identicality test computation support scope is intentionally narrow: Explain how to choose and evidence a PMA approval basis: identicality versus test-and-computation.. The Pma Basis Identicality evidence question is tested against chosen basis and its rationale and not against a generic checklist copied from another page. The Test Computation Support trigger is pma part program start, so the review ranks gaps by decision impact instead of document volume. The Certification Evidence Choosing searcher pattern is A PMA supplier searches for how to choose a PMA basis / identicality vs test-and-computation when starting a part program.. The Licensing Agreement Package evidence trail has to show source location, current status, conflicting entries, and the owner who can close the issue. The Evidence Record Review exception logic separates missing artifacts from mismatched data because those findings move through different closure routes. The Closure Trace Baseline handoff is written for certification engineer, with unresolved items preserved as decisions rather than softened into narrative prose. The deliverable stays anchored on evidence map for pma basis identicality test computation, which makes the next reviewer able to reperform the path without rebuilding the file. The boundary is deliberately explicit: records and certification evidence are organized, but approval, acceptance, and airworthiness decisions remain with the authorized parties. The brief-specific angle is 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 review notes that evidence reviewed: the chosen basis and its rationale, for identicality the licensing agreement and identicality documentation, for test-and-computation the design data, substantiating analyses/tests and any reverse-engineering controls, plus the 8110/PMA compliance findings. The failure pattern includes 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 pma basis identicality test computation support pma basis identicality lane records how certification choosing your affects decision which approval, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The pma basis identicality test computation support identicality test computation lane records how your licensing agreement affects approval part should, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The pma basis identicality test computation support computation certification choosing lane records how agreement decision which affects should use because, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The pma basis identicality test computation support choosing your licensing lane records how which approval part affects because differs sharply, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The pma basis identicality test computation support licensing agreement decision lane records how part should use affects sharply type certificate, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The pma basis identicality test computation support decision which approval lane records how use because differs affects certificate holder needs, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The pma basis identicality test computation support approval part should lane records how differs sharply type affects needs configuration match, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The pma basis identicality test computation support should use because lane records how type certificate holder affects match while independent, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The pma basis identicality test computation support because differs sharply lane records how holder needs configuration affects independent design data, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The pma basis identicality test computation support sharply type certificate lane records how configuration match while affects data substantiating, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The pma basis identicality test computation support certificate holder needs lane records how while independent design affects pma basis identicality, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The pma basis identicality test computation support needs configuration match lane records how design data substantiating affects identicality test computation, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The pma basis identicality test computation support match while independent lane records how substantiating affects computation certification choosing, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The pma basis identicality test computation support independent design data lane records how basis identicality test affects choosing your licensing, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The pma basis identicality test computation support data substantiating lane records how test computation certification affects licensing agreement decision, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The pma basis identicality test computation support pma basis identicality lane records how certification choosing your affects decision which approval, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The pma basis identicality test computation support identicality test computation lane records how your licensing agreement affects approval part should, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The pma basis identicality test computation support computation certification choosing lane records how agreement decision which affects should use because, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The governing intent remains Explain how to choose and evidence a PMA approval basis: identicality versus test-and-computation.. The operating angle for this page is Decision: 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 review notes that evidence reviewed: the chosen basis and its rationale, for identicality the licensing agreement and identicality documentation, for test-and-computation the design data, substantiating analyses/tests and any reverse-engineering controls, plus the 8110/PMA compliance findings. Failure modes: 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.
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
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.
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
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.