First Article Inspection and Configuration Management: AS9100 Explained

First Article Inspection (FAI) is the documented verification that a representative production part meets every engineering and design requirement before a supplier is allowed to run full production. Configuration Management is the parallel discipline that controls and records design changes across a part's entire service life — often decades, in aerospace. Together they are what lets an OEM trust a part built by a supplier it may never visit, which is why both sit at the center of AS9100 and its supporting standard, AS9102.

What First Article Inspection verifies — and why AS9100 requires it

An engineering drawing or specification can describe a part perfectly and still not guarantee that the tooling, process, and operator combination used to manufacture it actually produces that part. FAI closes that gap. It is a full, characteristic-by-characteristic inspection of one representative unit — pulled from a production run using production tooling and production processes, not a hand-built sample — checking that every dimension, material property, and special process called out on the drawing is actually being met.

AS9100 requires FAI as a condition of production approval because aerospace supply chains are long and layered: a tier-2 supplier's part gets built into a tier-1 assembly, which gets built into a system, which gets installed on an aircraft that will fly for 20-30 years. Nobody downstream re-verifies every characteristic of every incoming part. FAI is the point in the chain where "this supplier can reliably make this part to this drawing" gets proven and documented, once, before volume production starts.

The detailed requirements for what an FAI must contain and how it must be performed live in AS9102, "Aerospace First Article Inspection Requirement" — a standard referenced by AS9100 rather than embedded in it. Anyone implementing FAI at a supplier should treat AS9102 as the authoritative source for the current form structure, required data fields, and revision-specific details, since aerospace standards are periodically revised and the exact form content can change between editions.

The general structure of AS9102 documentation

At a general level, AS9102 organizes FAI records into three related forms, each covering a different layer of accountability. The intent, described here without asserting specific current field-by-field requirements, is roughly this:

• Form 1 — Part Number Accountability. Identifies the part, the drawing and revision it was built to, the supplier, and the overall accept/reject disposition of the first article.
• Form 2 — Product Accountability (materials and special processes). Documents the raw materials used and the special processes applied — operations like heat treatment, welding, plating, or non-destructive testing whose results can't be fully verified by inspecting the finished part alone, so the process itself has to be evidenced.
• Form 3 — Characteristic Accountability, Verification, and Compatibility. Lists the individual design characteristics from the drawing — dimensions, tolerances, notes — and records how each one was measured and whether it conforms.

These three forms exist because a part can look conforming and still fail for reasons a dimensional check alone won't catch — wrong alloy, a skipped heat-treat step, an out-of-tolerance feature nobody happened to measure. Confirming the exact fields, numbering, and current formatting each form requires belongs to AS9102 itself, not to a summary like this one.

What Configuration Management adds — and why it's non-negotiable in aerospace

FAI proves a part is right at one point in time. Configuration Management is what keeps it right afterward. It's the discipline of formally identifying a product's design baseline, controlling and recording every subsequent change to that baseline, and being able to state — for any unit ever built — exactly which drawing revision, which approved deviations, and which change history apply to it.

This matters more in aerospace than in most industries for two reasons that compound each other. First, service lives are long: a structural part or fastener design might stay in production and in service for decades, during which the drawing, the supplier, or the manufacturing process can all change multiple times. Second, the consequences of losing track of which configuration is installed where are safety-critical, not just a quality nuisance. If a design change is made and a part built to the old configuration is later found to be non-conforming with the new one, configuration management is what lets an organization trace exactly which serial numbers, on which aircraft, are affected — instead of grounding an entire fleet out of uncertainty.

A new FAI is typically triggered by configuration events: a design change affecting form, fit, or function; a change of manufacturing location or process; a lapse in production; or a change of supplier. That link between the two disciplines is deliberate — configuration management decides when the FAI baseline is no longer trustworthy and needs to be re-established.

Practical impact on suppliers and buyers

For a supplier, the practical weight of FAI and configuration management shows up long before an auditor arrives. Engineering, quality, and production have to agree on exactly which drawing revision a part is being built to before the first unit is cut — not after. Special processes need certificates from qualified sources, kept and cross-referenced, not just filed. Any deviation from the drawing, however minor it seems, needs a documented disposition rather than a verbal sign-off on the shop floor.

For a buyer or prime, the practical weight shows up in supplier evaluation. An FAI package that arrives complete, internally consistent, and traceable to the correct drawing revision is a meaningful signal about how seriously a supplier treats its own configuration control — and a package that's incomplete or inconsistent is often the first visible symptom of deeper documentation gaps that a routine audit alone wouldn't have surfaced yet.

Common mistakes

• Building the "first article" from a hand-picked or specially-made unit rather than a unit pulled from an actual production run using production tooling — which defeats the purpose of proving the process, not just the part.
• Treating FAI as a one-time event instead of re-triggering it after the configuration changes that are supposed to require it — a new supplier, a relocated process, a design revision.
• Losing the link between Form 3 characteristics and the drawing revision actually in effect when a drawing changes mid-production run, leaving the FAI record inconsistent with what's currently being built.
• Filing special-process certificates without cross-referencing them to the specific part, lot, or serial number they cover, which makes traceability collapse exactly when it's needed most — during a non-conformance investigation.
• Applying customer-specific requirements inconsistently — different OEMs (and different programs within the same OEM) can layer their own FAI and configuration expectations on top of AS9100/AS9102, and treating every customer identically is a common source of findings.

That's the general pattern behind Igera in an AS9100 environment: it doesn't try to replace AS9102, a quality engineer, or a customer's own requirements — it makes the supplier's own documentation searchable and answerable in seconds, with the exact source cited, instead of someone hunting through a shared drive during an audit prep.

Frequently asked questions

Is First Article Inspection a one-time requirement for a part?

No. FAI establishes a baseline for a given part, drawing revision, process, and supplier combination. Significant configuration changes — a design revision affecting form, fit, or function, a change of manufacturing location or process, a break in production, or a change of supplier — typically require a new or partial FAI, because the original baseline no longer reflects how the part is currently being made.

What's the difference between FAI and a routine incoming or in-process inspection?

Routine inspection checks that individual parts conform to the drawing, usually via sampling or key characteristics. FAI is a full verification of essentially every characteristic on one representative unit, specifically to prove the process itself — tooling, method, and materials — is capable of producing a conforming part before volume production begins.

Do all three AS9102 forms apply to every part?

Not necessarily to the same depth. Simpler parts with no special processes may involve a lighter Form 2, for instance. The applicability and detail required for each form depend on the part's complexity and the specific customer requirements layered on top of AS9102 — which is exactly why AS9102 itself, not a general summary, should be consulted to confirm what applies to a specific part.

Why do different OEMs (VW-style tiering, Ford, or in aerospace, Boeing/Airbus-tier customers) have different FAI expectations?

AS9100 and AS9102 set the baseline, but individual OEMs and prime contractors commonly layer customer-specific requirements (CSRs) on top — additional documentation, approval workflows, or characteristic-verification detail specific to their programs. A supplier serving multiple aerospace customers often has to satisfy several overlapping but not identical FAI expectations simultaneously.

Who is responsible for triggering a new FAI when a design changes?

Responsibility is typically shared: the supplier's configuration management process should flag when a change meets the threshold for re-verification, and the customer's engineering or quality function often has its own approval gate for the same change. In practice, this is a point where clear internal procedures matter — ambiguity here is a common source of audit findings.

What happens if a non-conforming characteristic is found during FAI?

The specific characteristic is documented as non-conforming on the applicable form, and the article is not accepted as representative of a validated process until the issue is resolved — through rework, a corrective action on the process, or a formally approved deviation, depending on the nature of the non-conformance and what governs the specific program.

Is FAI required for every supplier in the chain, or only the prime?

AS9100-certified organizations generally flow FAI requirements down through their own supply chain via purchase order requirements, so it isn't limited to prime contractors. A tier-2 or tier-3 supplier producing an AS9100-controlled part will typically face the same FAI obligation as a tier-1 supplier, scaled to what their contract and the applicable drawing require.