PMA article data
Means-of-compliance map support for a PMA article approval package
This review works through the means-of-compliance map that tells the FAA how each requirement in a PMA article package will be shown met. A certification engineer tests the logic from requirement to method to evidence, confirming that every requirement assigned a means also has an evidence path that leads somewhere real and finished. It catches requirements given a method on paper with no data actually produced behind them. You receive a gap assessment, a requirement-to-evidence map, and a closure plan before the package moves toward approval.
When this review is needed
- A means-of-compliance map is assembled and the team wants each method confirmed to lead to finished evidence.
- Some requirements carry a method chosen at planning that no one has since produced data for.
- Methods were reassigned mid-program and the evidence paths need to be re-walked.
- The map feeds the compliance matrix and its logic must be sound before the matrix is finalized.
The problem
Assigning a means of compliance is a planning act, and planning outruns evidence. A requirement gets marked for test, analysis, or inspection, the row looks handled, and then the program never circles back to confirm the data was produced and closed. Methods also get swapped as the design settles, but the map often keeps the original assignment, so a requirement can point at an evidence path that was abandoned while a second, real path goes unrecorded.
What gets reviewed
- Each requirement's assigned means checked for an evidence path that exists and is complete
- Requirement-to-method-to-evidence logic tested end to end for every mapped item
- Method reassignments reconciled so the map reflects the path actually taken
- Requirements assigned a means with no data produced flagged as open paths
- Method appropriateness confirmed so no requirement leans on an ill-suited approach
- Shared evidence checked where one report is claimed against multiple requirements
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
- Every requirement with an assigned means has an evidence path that terminates in real data
- Each method fits the requirement it is mapped to and the way it must be shown met
- Reassigned methods leave no orphaned path and no requirement pointing at abandoned work
- Evidence claimed against multiple requirements genuinely supports each one
- The map's logic agrees with the compliance matrix it feeds
Evidence normally required
- The current means-of-compliance map for the article
- The applicable requirement set the map is built against
- The evidence deliverables each method is supposed to produce
- The change history showing where methods were reassigned
- The compliance matrix the map feeds, if it already exists
Common discrepancies
- Requirements assigned a means with no data ever produced behind them
- Methods reassigned in practice while the map keeps the original path
- One test report claimed against requirements it does not fully cover
- A method chosen that does not suit how the requirement must be demonstrated
What is at stake
A method with no evidence behind it is an empty promise the FAA discovers by following the path to its end and finding nothing. Each dead path becomes a request for data and a schedule slip, and a map full of them signals that the package was planned but not finished, which invites a harder look at everything else in the submission.
How the work runs
Read the assignments
List every requirement and the means of compliance assigned to it in the current map.
Follow each path
Trace requirement to method to evidence end to end and confirm each path finishes in real data.
Reconcile reassignments
Where methods were swapped, retire the abandoned path and record the one actually taken.
Deliver the map and plan
Provide a requirement-to-evidence map and a closure plan for the paths still open.
What the buyer receives
- A gap assessment listing every requirement whose evidence path is incomplete
- A requirement-to-evidence map showing each method's finished data path
- A closure plan for the open paths and the reassignments to reconcile
Who uses the output
- Certification leads confirming the map's logic before it feeds the matrix
- Quality leads verifying claimed evidence exists and covers its requirements
- Engineers producing the data for the paths still shown open
How the work fits into the transaction or program
The means-of-compliance map is the logic layer between requirements and evidence, and it feeds the compliance matrix directly. Checking it before the matrix is locked keeps the whole package coherent, because a broken evidence path here becomes a false matrix row later.
Start with a single asset
Reduce finding cycles by checking the package first.
Jurisdiction-specific considerations
This work is scoped to PMA approval under the FAA framework, where the applicant selects the means and shows each requirement met by an agreed method. The review keeps the mapping in FAA terms and does not restate it for a different authority's compliance process.
Regulatory limits
This review assesses whether the assigned means lead to real, complete evidence. It does not select the means on the applicant's behalf, does not make a compliance finding, and does not grant PMA or any airworthiness approval.
What this review does not cover
- Producing the test, analysis, or inspection evidence a path requires
- Negotiating acceptable means of compliance with the FAA
- Building or finalizing the compliance matrix the map feeds
Specific to this review
- A means-of-compliance map fails most often at the last hop: the method is assigned but the evidence path stops before real data.
- Method reassignments are silent killers because the abandoned path stays in the map while the real one goes unrecorded.
- Evidence shared across requirements needs per-requirement checking; a report that covers one condition rarely covers every claim made on it.
- Because the map feeds the matrix, an error caught here saves fixing the same error in a downstream document twice.
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.
SAE International. Development assurance process at aircraft and system level, including requirements capture and validation.
Frequently asked questions
Is this the same as reviewing the compliance matrix?
No, it sits one step upstream. The matrix records that a requirement is met and cites the evidence; this review tests the logic that gets there, confirming each assigned method actually leads to finished data. Sound map logic is what keeps the matrix from carrying a row that looks complete but has no real path behind it.
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.