Conformity records evidence review for aircraft modifiers

When this review is needed

• A test report claims credit against a specimen whose drawing revision at test time was never captured in a conformity statement.
• A ground or flight test article was reworked between conformity inspection and test, and the record does not show the change was re-inspected.
• The authority has raised a finding asking which configuration a passing test actually demonstrated.
• A design change is about to alter a part that earlier conformity evidence relied on, and the modifier needs to know what re-conforming it will cost.

The problem

Conformity is the hinge that turns a test result into approved-data credit, and it is the first thing to slip when a program runs late. Articles get built, tested, and modified faster than the paperwork that pins each one to a drawing state, so a report can pass its test while the specimen it was run on drifts away from any controlled configuration. By submittal the modifier holds a stack of conformity statements that read fine one at a time but do not connect the tested hardware to the design the credit is claimed against.

What gets reviewed

• Each conformity statement matched to the drawing revision and part identity in force at the time of test or inspection
• Test-article conformity reconciled to the specific report that claims credit from it
• Rework and repair between conformity and test checked for a re-inspection record
• Installation conformity tied to the modification drawing and effectivity it demonstrates
• Article serial and part numbers reconciled across conformity, build, and test records
• Open or conditional conformity entries traced to the disposition that cleared them

What gets validated

• Every crediting test report cites a conformity statement covering the exact article configuration under test
• The drawing revision named on each conformity matches the revision the certification basis controls at that date
• Rework performed after a conformity inspection carries a re-inspection or an accepted disposition
• Part and serial numbers on the conformity agree with the build record and the report specimen
• No conformity statement references a drawing state that was superseded before the inspection occurred

Evidence normally required

• The conformity statements and inspection records for test articles and installations
• The controlled drawing tree with revision dates for the modified configuration
• Test reports that claim credit from a conformed article
• Build, rework, and repair records for each test specimen
• The effectivity and part-numbering scheme for the modification

Common discrepancies

• A test report crediting an article whose post-conformity rework was never re-inspected
• A conformity statement citing a drawing revision superseded before the inspection date
• An installation conformity whose effectivity does not match the serial it was recorded against
• A serial number on a conformity that cannot be reconciled to the build record for that article

What is at stake

A test whose article cannot be tied to a controlled configuration is a test the authority can decline to credit, which sends the modifier back to re-conform or re-run at the worst point in the schedule. An installation conformity that references a superseded drawing can invalidate the compliance finding built on it, and reconstructing which revision was actually inspected months later is often impossible.

How the work runs

What the buyer receives

• A gap list flagging each conformity that fails to tie its article to a controlled configuration
• An evidence map linking every crediting test to the conformity and drawing state behind it
• A closure sequence ordering the re-conformity and disposition work by its effect on submittal

Who uses the output

• STC program managers deciding which conformity gaps must close before the package moves
• Certification leads answering an authority's question about which configuration a test demonstrated
• Engineering owners judging whether a specimen has to be re-conformed or re-tested

How the work fits into the transaction or program

Conformity records sit under nearly every test-based compliance finding, so a break here propagates upward into the compliance matrix and the means-of-compliance map. Checking it before submittal lets the modifier close a configuration gap on its own schedule, and the evidence map it produces gives the rest of the data package a firm article-to-configuration link to build compliance claims on.

Jurisdiction-specific considerations

FAA and EASA both expect test credit to rest on a conformed article tied to controlled data, but the form of the conformity record and who may sign it differ between the two systems. Where a modification is aimed at both authorities, the review notes where a conformity accepted under one basis needs additional signature or documentation to carry under the other.

Regulatory limits

The review confirms conformity records are internally consistent and tie tested hardware to a controlled configuration. It does not perform conformity inspections, sign a conformity statement, or make any determination that an article or its test is acceptable to an authority.

What this review does not cover

• Performing or re-performing conformity inspections on any article
• Re-running a test whose conformity link is broken
• Any determination that a tested article is approvable

Specific to this review

• Conformity is time-stamped evidence: it proves the article matched a drawing at a moment, so a later revision to that drawing does not retroactively cover an earlier test.
• Rework between conformity inspection and test is the most common way a passing test loses its credit, because the tested article no longer matches the conformed one.
• Reconstructing which drawing revision an article was conformed to, after the fact, is usually impossible, which is why the check runs before submittal rather than during a finding response.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits