Learn exactly what is first article inspection, when it's needed, & how it works. A complete 2026 guide for engineers, designers, & supply chain managers.
You sent out a tight-tolerance part for prototype machining. The CAD is clean, the drawing looks complete, and the supplier says they can make it. A week later, the parts arrive and one critical bore is off, a datum was interpreted differently than you intended, or the material cert doesn't match the purchase spec. None of those failures are dramatic on their own. Together, they can stall a build, burn budget, and force a rushed redesign conversation that should have happened before chips were cut.
That's where first article inspection earns its keep.
For teams ordering anywhere from one to low-volume quantities, FAI can feel like paperwork borrowed from aerospace. Sometimes it is overkill. Sometimes it's the cheapest insurance in the whole project. The practical question isn't whether FAI sounds formal. It's whether you need proof that the supplier's process, setup, documentation, and interpretation of your design are aligned before you trust the next batch.
Table of Contents
- FAI validates the process, not just the part
- Why it matters for prototype and low-volume orders
- When a partial FAI is usually enough
- Step 1 Review the complete requirement set
- Step 2 Build a production-representative sample
- Step 3 Balloon the drawing and map every requirement
- Step 4 Measure, verify, and record actuals
- Step 5 Review discrepancies before release
- Step 6 Approve the package and lock the baseline
- The documents that matter most
- The AS9102 form logic in plain language
- The metrology tools behind the report
What Is First Article Inspection and Why It Matters
What is First Article Inspection? In practice, it's a structured check that confirms a supplier can build a production-representative part to the full design definition before you rely on that process. The point isn't to admire the first finished piece. The point is to verify that the manufacturing method, tooling, measurement approach, and documentation all line up with the drawing and requirements.
The cleanest way to think about FAI is as a dress rehearsal for production. If the rehearsal exposes a missed note, wrong revision, bad setup, or material mismatch, you fix it before it multiplies into scrap, rework, or field problems.
FAI became formalized through AS9102, first published in 2003 by SAE International for the aerospace industry, where it was defined as a structured method to verify that the first production item meets all requirements before full-rate production begins, as described by Criterion Precision's overview of AS9102 and aerospace FAI.
FAI validates the process, not just the part
Many new designers encounter difficulties at this stage. A single acceptable sample doesn't automatically prove the process is under control. A machinist can nurse one part through with extra attention, selective deburring, or manual touch-offs. That may be enough for a prototype fit check, but it's not enough if you need confidence in repeatability.
A real FAI asks harder questions:
- Was the correct revision used: Did manufacturing build from the latest drawing, notes, and contract requirements?
- Was the right process followed: Were material, routing, special processes, and inspection methods consistent with the intended build path?
- Do the records support the result: Can the supplier show the measured values, certs, and traceability that back up the claim of conformance?
**Practical rule:** If failure would force a redesign review, assembly delay, or customer explanation, don't rely on a casual “we checked the first one.”
For rapid prototyping, that doesn't always mean a full aerospace-style package. It does mean you should decide how much evidence you need before release. On a simple bracket with loose tolerances, a targeted dimensional report may be enough. On a sealing surface, optical mount, medical component, or mating part with tight GD&T, a deeper first article review is usually justified.
Why it matters for prototype and low-volume orders
Low-volume buyers often assume FAI only matters once production ramps. That's backwards. Early builds are where interpretation errors are most common because the design, manufacturing plan, and inspection method are all new.
This matters even more in new product introduction workflows, where the handoff from design to manufacturing tends to expose the first real mismatch between what the model implies and what the shop can repeatedly hold.
The cheapest time to discover a wrong datum strategy is before the supplier makes the rest of the lot.
When to Perform an FAI and Key Industry Standards
The practical trigger for FAI isn't “whenever quality asks for it.” It's whenever something has changed enough that previous evidence no longer gives you confidence. For buyers working on prototypes or bridge builds, that usually comes down to risk, not bureaucracy.
A commonly used set of triggers includes new part introduction, engineering changes, supplier or site transfers, and production gaps of two years or more, as outlined in Deltek's manufacturing guidance on First Article Inspection. That two-year threshold matters because it reflects a simple reality. Processes drift, tooling changes, people move, and old approvals go stale.
When a full FAI is worth it
A full FAI makes sense when you're trying to establish a baseline for a part that hasn't yet earned trust. That usually includes first builds of a new part number, first builds at a new supplier, or parts with tight tolerances where one misunderstanding can affect function.
Use a full FAI when:
- The part is new: No prior build history exists for this exact design and revision.
- The feature stack is unforgiving: Think mating bores, true position callouts, sealing faces, or cosmetic Class A surfaces.
- The supplier is new to the part: Even a capable shop can interpret your drawing differently than the last one.
- The build has compliance consequences: Aerospace, medical, defense, and other controlled applications often require formal evidence.
When a partial FAI is usually enough
Not every revision deserves a full reset. If you changed one non-critical chamfer note, switched a non-functional marking, or updated a feature that doesn't affect fit, form, or function elsewhere, a scoped or partial FAI is often the smarter move.
That approach works best when the buyer and supplier agree on exactly what changed and what must be reverified. What doesn't work is asking for “just inspect the changed feature” when the change also affects fixturing, datums, or process routing.
If the change touches how the part is held, located, or measured, the impact is usually wider than the redline suggests.
AS9102 vs PPAP at a Glance
| Aspect | AS9102 (Aerospace) | PPAP (Automotive) |
|---|---|---|
| Primary purpose | Formal first article verification before production release | Broader production part approval framework |
| Typical use | Aerospace and defense supply chains | Automotive supply chains |
| Core emphasis | Structured accountability for part, product, and characteristics | Evidence that the production process can support approved production |
| Reporting style | Three defined forms and drawing-linked accountability | Broader submission package, usually tied to automotive customer requirements |
| Best fit for prototype buyers | Useful when you need detailed first-build traceability | Useful when your supplier already works in automotive approval systems |
For most prototype buyers, the practical difference is simple. AS9102 is a dedicated FAI format. PPAP is a wider approval system that can include first-article-type evidence but goes beyond it. If your CNC supplier serves mixed industries, you may hear both terms. Ask which deliverables you'll receive.
A lot of low-volume CNC work sits between “prototype only” and “production approved.” That's why buyers often benefit from reading FAI requirements alongside low-volume CNC machining considerations. The volume is low, but the tolerance risk can still be high.
The Step-by-Step First Article Inspection Process
Most FAIs go wrong before inspection starts. The root issue is usually poor requirement review, not poor measurement. If the supplier builds from the wrong revision, misses a note, or treats a prototype setup as if it were production intent, the report will only document the confusion.
Step 1 Review the complete requirement set
Before a machine runs, someone needs to reconcile the drawing, CAD model, material callout, revision level, finish requirements, and any purchase order quality clauses. This sounds basic, but it's where many first articles are unknowingly compromised.
A good review catches questions like these:
- Which document controls: The model, the 2D drawing, or both?
- Are all special processes defined: Heat treat, anodize, passivation, welding, marking, or cleaning requirements must be explicit.
- Are datums and GD&T usable in inspection: If the drawing is technically correct but awkward to fixture or measure, clarify it now.
Step 2 Build a production-representative sample
The first article should reflect the process you intend to use, not a one-off hero part. That means production-intent tooling, normal workholding, planned machines, and the intended process flow.
This is especially important in rapid prototyping, where shops sometimes mix prototype shortcuts with future production assumptions. If the part that passed inspection was made differently than the parts you'll reorder, the FAI has limited value.
Step 3 Balloon the drawing and map every requirement
In a formal FAI, the inspection package typically includes a ballooned drawing and three structured forms covering part-level accountability, product accountability for materials and processes, and characteristic accountability, with measured actuals recorded against every specified dimension and note, as described in QC Advisor's guide to FAI packages and reporting.
Ballooning means assigning an identifier to each requirement so every dimension, note, and attribute has a clear inspection record. This is what keeps the report from turning into a pile of disconnected measurements.
A useful video overview of the process helps if you haven't seen the workflow in practice:
Step 4 Measure, verify, and record actuals
This is the point commonly associated with FAI, but it's only one part of the job. Measurement includes dimensional checks, yes, but also material verification, process evidence, and any required functional checks.
What matters here is disciplined recording. “Pass” by itself isn't enough for critical work. The report should tie each ballooned requirement to an actual result and the method used to verify it.
- Dimensional features: Sizes, locations, profiles, flatness, perpendicularity, and other drawing-defined characteristics.
- Material evidence: Certifications and traceability to the specified material.
- Process evidence: Documentation for outside processing or special process steps.
- Functional checks: Fit, movement, leak, continuity, or performance verification if the design requires it.
A good FAI report lets another engineer reconstruct what was checked, how it was checked, and why the supplier concluded the part conformed.
Step 5 Review discrepancies before release
If something is out of tolerance, the right next step isn't to ship and apologize. It's to stop, contain the issue, and determine whether the problem came from setup, programming, drawing interpretation, measurement method, or the design itself.
On prototype jobs, this review often reveals valuable DFM feedback. Maybe the tolerance is valid but expensive to hold with the current geometry. Maybe a note is ambiguous. Maybe the inspection datum scheme doesn't match how the part functions in assembly.
Step 6 Approve the package and lock the baseline
Once the buyer accepts the FAI, that report becomes the baseline for future builds of that revision. It gives both sides something concrete to work from. If the next batch drifts, you can compare against a documented standard instead of relying on memory or email threads.
That's the value of the process. A passing FAI doesn't end quality control. It establishes a shared reference point that makes the next conversation faster and more objective.
Anatomy of an FAI Report Deliverables and Tools
An FAI is only as useful as the package it leaves behind. If the report doesn't clearly connect the design requirement to the measured result, it won't help much during approval, reorder review, or an audit trail later.
The documents that matter most
A usable FAI package usually has a small number of core deliverables, each doing a distinct job.
- Ballooned drawing: This is the index. Every requirement gets an identifier so the drawing and the report speak the same language.
- Dimensional results: These are the measured actuals tied back to the balloon numbers.
- Material and process records: These confirm that the part wasn't merely shaped correctly, but also made from the right inputs and processed correctly.
- Functional or special test evidence: If the part has performance requirements, those results belong in the package too.
For buyers, the fastest way to review a package is to start with the ballooned drawing and spot-check whether the dimensional report really maps to it cleanly. If the numbering is inconsistent or key notes aren't represented, the package probably needs clarification.
The AS9102 form logic in plain language
Even if you're not in aerospace, the AS9102 form structure is useful because it separates accountability into logical buckets:
| Deliverable | What it tells you | Why it matters |
|---|---|---|
| Form 1 style data | Which part and revision were inspected | Prevents approval against the wrong configuration |
| Form 2 style data | Which materials, processes, and tests apply | Confirms the part was made the right way |
| Form 3 style data | Which characteristics were measured and what the results were | Shows whether the part matches the design definition |
That structure helps prototype teams too. It forces the conversation away from “the part looks fine” and toward “which requirement was verified, by what evidence, and against which revision?”
The metrology tools behind the report
The report doesn't generate itself. Behind it are inspection tools and methods that need to fit the geometry and tolerance stack of the part.
Common tools include:
- CMM systems: Useful for complex geometry, positional relationships, and repeatable data capture.
- Calipers and micrometers: Still effective for straightforward linear dimensions when the tolerance and access make sense.
- Go or no-go gauges: Good for specific acceptance checks when designed correctly.
- Optical or scan-based systems: Helpful for contours, complex surfaces, or faster data collection on hard-to-reach features.
The modern FAI report is moving from paper toward digital traceability, with stronger links between CAD data, CMM output, and supporting records. Boeing's supplier requirements explicitly call out extracting design characteristics from digital product definition for the FAI report, which reflects the shift toward integrated workflows rather than disconnected paperwork, as shown in Boeing's supplier quality requirements for FAI and digital product definition.
That shift matters when you're dealing with complex tolerances discussed in this CNC machining tolerances guide. The tighter and more relational the geometry, the less you want manual transcription sitting between the model and the inspection result.
The best FAI packages are easy to audit because the data path is obvious. Requirement, method, result, evidence.
Common FAI Failure Modes and Corrective Actions
When an FAI fails, the failure itself isn't the disaster. The problem is misreading the failure as bad luck instead of useful evidence. A failed first article tells you where the manufacturing system and the design handoff stopped agreeing.
Setup errors
These happen when the shop uses the wrong fixture logic, tool offsets, workholding strategy, or machine setup. A classic example is a hole pattern that shifts because the part was located from a convenient edge instead of the true datum scheme.
Corrective action usually means rebuilding the setup method, not just remachining the part. If the datum strategy was wrong, the inspection result is telling you the process reference frame is wrong too.
Programming errors
CAM and post-processing mistakes show up as missing features, mirrored geometry, incorrect depths, wrong cutter compensation, or paths generated from an outdated model revision.
The fix here is disciplined program control. Review the source model, regenerate the toolpath if needed, verify revision control, and run a controlled first-off after correction. If the supplier can't explain which program version cut the part, expect repeated trouble.
Interpretation errors
These are common in prototype work because the drawing is new and the designer may have assumed too much context. Typical examples include misread GD&T, an overlooked note, or a finish callout applied to the wrong surface set.
At this stage, buyer and supplier need a direct technical conversation. Sometimes manufacturing misread the requirement. Sometimes the drawing left too much room for interpretation. The corrective action may be training, drawing clarification, or a design revision.
If two competent people read the same note differently, treat that as a documentation problem, not just an operator problem.
Material and process errors
A part can hit dimension and still fail first article because the wrong material grade was used, a required process cert is missing, or a special process route wasn't followed.
Corrective action starts with containment and traceability review. Identify what material and processing touched the part, isolate affected pieces, and rebuild the documentation chain. If the issue is a cert mismatch, don't paper over it. Resolve the underlying traceability gap before approval.
A Practical FAI Checklist for Buyers and Suppliers
For low-volume work, the most useful FAI habit is deciding the scope before the chips fly. Buyers often ask for a “full FAI” without defining what that means. Suppliers often promise inspection without confirming what evidence will be delivered. Both create friction.
The decision to require FAI is a risk-management choice balancing cost and time, and the U.S. Federal Acquisition Regulation directs contracting officers to consider the effect on cost and delivery schedule before requiring first article testing and approval, as stated in FAR Subpart 9.3 on first article testing and approval.
Checklist for buyers
- Define the scope in the PO: State whether you need a full FAI, a partial FAI, or a dimensional report on selected critical features.
- Send controlled design data: Make sure the supplier has the right revision of the drawing, model, notes, and material requirements.
- Flag critical features early: Don't assume the shop knows which tolerances drive function, sealing, alignment, or assembly success.
- Agree on submission timing: Decide whether approval is required before shipment or before the next batch starts.
- Review the report promptly: A delayed buyer review can stall production just as badly as a delayed supplier submission.
Checklist for suppliers
- Confirm requirements before machining: Resolve revision mismatches, note conflicts, and ambiguous GD&T before the run.
- Use suitable, calibrated inspection methods: Match the tool and method to the tolerance and geometry.
- Keep traceability intact: Material, process steps, and measurement records should all tie back to the inspected part.
- Document actuals clearly: Make it easy for the buyer to compare requirement versus result.
- Escalate discrepancies early: A fast question before shipment is better than a nonconformance after receipt.
If you need a manufacturing partner that can support rapid prototypes, low-volume runs, and tight-tolerance inspection with clear communication, LC Proto is built for that kind of work. Their team supports CNC machining and prototyping projects where design intent, speed, and traceable quality all need to coexist.
