Field approval data
Compliance matrix support for an FAA field approval
This review readies the compliance matrix that anchors a field-approval data package, confirming it covers every applicable regulation, assigns a defensible means of compliance to each, and cites evidence that still supports the claim. It is run by or for a modifier or operator assembling the data an inspector will use to approve an alteration on Form 337. It checks that the certification basis is complete for the alteration, that no applicable paragraph is left uncovered, and that every cited report or analysis is the current revision rather than a superseded one. You get a gap assessment, an evidence map from each matrix line to its source, and a closure plan for the entries that cite stale or missing evidence.
When this review is needed
- A modification is going to an inspector for field approval and the matrix has to show complete regulatory coverage.
- The certification basis for the alteration was assumed rather than derived and may miss an applicable paragraph.
- Evidence cited in the matrix comes from an earlier revision and may no longer support the claim as written.
- A prior field-approval attempt on a similar alteration stalled on coverage the inspector found incomplete.
The problem
A compliance matrix looks complete when every row has an entry, but completeness is about the rows that are missing, not the ones that are filled. The certification basis for a field-approved alteration is often carried over from a template or a similar job, so an applicable regulation particular to this installation never makes it onto the matrix. Meanwhile the evidence column ages: a report cited when the matrix was built gets revised, and the citation keeps pointing at a version that no longer says what the matrix claims.
What gets reviewed
- The certification basis derived for this specific alteration, not carried from a template
- Every applicable regulatory paragraph present as a row with an assigned means of compliance
- The means of compliance chosen for each requirement checked for defensibility at field-approval level
- Each evidence citation confirmed as the current revision that still supports the claim
- Environmental qualification against DO-160G referenced where the installation environment demands it
- System-level requirements handled consistently with ARP4754B where the alteration adds function
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
- The matrix's certification basis accounts for every regulation applicable to this alteration and installation
- No applicable paragraph is absent from the matrix or left without a means of compliance
- Each means of compliance is one an inspector can accept for a field approval, not one reserved for a type-certificate program
- Every evidence citation resolves to the current revision of the report or analysis
- Cited environmental qualification categories match the installation's actual environment
Evidence normally required
- The draft compliance matrix and its certification-basis assumptions
- The alteration description, drawings, and affected-area definition
- The reports, analyses, and test results the matrix cites as evidence
- The applicable regulatory sections for the aircraft and the alteration
- Any prior field-approval correspondence on a comparable alteration
Common discrepancies
- An applicable regulation missing from the matrix because the basis was carried from a template
- An evidence citation pointing at a report revision that has since been superseded
- A means of compliance that suits a type-certificate program but not a field approval
- An environmental qualification category cited that does not match the installation location
What is at stake
An inspector who finds one applicable paragraph missing from the matrix stops trusting the coverage and works the whole package harder, which turns a field approval into an extended back-and-forth. A matrix that cites superseded evidence is worse: the claim reads as supported until someone opens the referenced report and finds it does not support the finding, at which point the alteration's approval basis is in question rather than merely incomplete.
How the work runs
Derive the basis
Build the certification basis from the alteration itself so no applicable regulation is missing from the matrix.
Assign the methods
Confirm each means of compliance is one an inspector can accept for a field approval.
Refresh the citations
Check every evidence reference resolves to the current revision that supports the claim.
Close the gaps
List rows without coverage or with stale evidence and sequence the corrections before submission.
What the buyer receives
- A gap assessment of regulatory coverage and evidence currency across the matrix
- An evidence map linking each matrix line to its current supporting source
- A closure plan for the rows that lack coverage or cite stale evidence
Who uses the output
- Engineering leads confirming the matrix presents complete coverage before it reaches an inspector
- Compliance staff reconciling each cited report to its current revision
- Maintenance leadership deciding whether the alteration's basis is ready for field approval
How the work fits into the transaction or program
The compliance matrix is the inspector's map through a field-approval package: it says which regulations apply, how each is met, and where to find the proof. This review runs before the package reaches the inspector, so missing coverage and stale citations are fixed while the modifier still controls the data, rather than surfacing as inspector findings that stall the Form 337 approval.
Start with a single asset
Reduce finding cycles by checking the package first.
Jurisdiction-specific considerations
A field approval is an FAA mechanism, and the acceptable means of compliance available to an inspector for a one-off alteration are narrower than those open to a type-certificate or STC applicant, so the matrix has to select methods an inspector can actually accept. Where the same modification will later be pursued as an STC or replicated on a different register, the review notes where the field-approval evidence would need strengthening to carry into the broader approval.
Regulatory limits
The review checks that the matrix covers the applicable regulations and cites current supporting evidence. It does not approve the alteration, sign a Form 337, determine airworthiness, or bind an inspector to accept the certification basis or any means of compliance in the matrix.
What this review does not cover
- Obtaining the field approval or signing the Form 337
- Developing new test or analysis evidence to fill a coverage gap
- Any airworthiness determination on the altered aircraft
Specific to this review
- A compliance matrix fails on the rows that are absent, not the ones that are filled, so the review's real work is deriving the basis rather than reading the entries.
- Field approval limits the means of compliance an inspector can accept, so a method valid for an STC program can still be wrong for the matrix.
- Evidence citations decay silently as reports are revised, so a matrix that was correct at build can point at unsupported versions by submission.
Sources
U.S. Government (eCFR). Type certificates, STCs (Subpart E), TSO authorizations (Subpart O), PMA (Subpart K), and export airworthiness approvals (Subpart L).
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
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
How is a field-approval matrix different from an STC compliance matrix?
The regulations may overlap, but the means of compliance an inspector can accept for a one-off field approval are narrower than those available in a type-certificate or STC program. A method that is fine for an STC can be one an inspector cannot accept for a Form 337, so the matrix is scoped to what the field-approval path allows.
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.