CMM Programming for First Article Inspection
When a new aerospace or precision component moves from the drawing to the production floor, the first article inspection is not a formality. It is the documented proof that your manufacturing process can actually produce what the design requires. The problem most shops face is not the inspection itself. It is the time it takes, the risk of a rejected FAIR package, and the pressure to not let quality bottlenecks kill a delivery promise. CMM programming done correctly addresses all three of those issues at once. This article covers how to structure CMM-driven first article inspection to meet AS9102 requirements without letting lead times slip.
Table of Contents
Quick Takeaways
Key Insight
Explanation
AS9102 Rev C requires three distinct forms
Form 1 covers part number accountability, Form 2 covers product accountability (materials and processes), and Form 3 covers characteristic accountability. Every balloon on your drawing must trace to a line on Form 3, and CMM output must map to those same balloon numbers.
Offline CMM programming eliminates machine idle time
Developing the measurement routine against a 3D CAD model before the physical part arrives means the CMM runs inspection the moment the first piece comes off the machine, not hours later while a programmer teaches probe paths.
Balloon numbering discipline prevents most FAIR rejections
The balloon number on the drawing and the characteristic number on Form 3 must match exactly. A single numbering mismatch makes the package non-auditable and forces a resubmission cycle.
CMM output must be imported, not manually transcribed
Transcribing CMM data by hand introduces transcription errors and adds hours to a FAIR cycle. Import CMM results directly into your FAIR software or documentation template to eliminate that risk.
A pre-submission internal audit catches most rejections before the customer does
A structured checklist review by someone other than the preparer, checking drawing revision match, balloon-to-Form 3 coverage, and signature completeness, consistently prevents the 5-to-15 business day penalty of a rejected submission.
CMM programming time for new parts should be budgeted separately
Initial CMM program development on a new part geometry adds significant time compared to running an existing program. This must be factored into project scheduling, not absorbed as overhead after a delivery commitment is made.
AS9102 applies to the process, not just the part
The standard requires evidence that the production process is capable of repeatedly producing conforming parts. A single part measurement without documented process traceability does not satisfy the standard.
What AS9102 Actually Requires From Your FAI Package
AS9102 is the North American aerospace standard governing first article inspection requirements. It has counterparts in other regions, but in the North American aerospace and defense supply chain, AS9102 is the reference. The current revision is Rev C, released in June 2023, which brought the standard into closer alignment with AS9100, the quality management system standard for the aerospace industry.
A compliant First Article Inspection Report (FAIR) under AS9102 contains three forms, each with a specific accountability scope. Form 1 identifies the part and any associated sub-assemblies. Form 2 accounts for all material and process specifications, special processes, and functional testing requirements defined in the design. Form 3 accounts for every product characteristic, including every dimension, GD&T callout, surface finish specification, and drawing note, with measured values and objective evidence for each.
Form 3 is where CMM programming does most of its work. The standard requires that the inspection drawing or model show every characteristic with a uniquely numbered balloon, and those balloon numbers must match the characteristic numbers on Form 3 exactly. That link is what makes the report auditable. A mismatch, even a single transposed number, breaks the audit trail and can invalidate the entire package.
When a New FAIR Is Required
A FAIR is not a one-time event for a part number. It is triggered by new part introduction, design revision changes that affect characteristics, material or supplier changes, and manufacturing location changes. For precision machined aerospace components, even a change in tooling strategy or fixturing approach can require a partial or full re-inspection depending on the customer's contract requirements. Building a reusable CMM program from the start means those re-inspection events do not start from scratch.
A rejected FAIR does not just delay delivery. It signals a process problem to the customer's quality team, and rebuilding that confidence takes longer than the paperwork cycle itself.
Where CMM Programming Fits in the FAI Workflow
The FAI process moves through distinct stages: planning, ballooning the drawing, building the inspection plan, producing the part, measuring it, collecting results, and compiling the documentation package. CMM programming is concentrated in the measurement and results collection stages, but decisions made during planning and ballooning directly determine how efficient that measurement stage will be.
Ballooning First, Programming Second
A common mistake is to begin CMM programming before the ballooned drawing is finalized. The CMM program must reference the same characteristic numbering that appears on Form 3. If balloon numbers change after the CMM program is built, every feature assignment in the program has to be audited and corrected. The right sequence is: finalize the ballooned drawing, extract the characteristic list for Form 3, then build the CMM program using those exact characteristic identifiers as measurement labels.
Modern inspection planning software can extract feature information, including nominals, tolerances, and GD&T callouts, directly from the drawing during the ballooning step. That extracted data becomes the skeleton of Form 3 and the input for the CMM program simultaneously. Shops that run this process in sequence rather than in parallel add days to their FAIR cycle unnecessarily.
Probe Path and Fixture Planning
For complex aerospace components with deep pockets, tight bores, or compound-angle features, probe path planning is not a minor detail. A poorly planned probe path produces collision risks, requires repeated manual intervention during the measurement run, and generates inconsistent results when different operators run the same program. Part fixturing must be designed in parallel with CMM program development. If the part moves between measurements, all data from that run is suspect, and you are back to re-measuring.
Pro tip: Design your CMM fixture to reference the same datum structure used in machining. If the part is held on datum A, B, C during milling, your CMM setup should replicate that datum scheme. Misaligned datums between machining and inspection are a leading cause of parts that appear out of tolerance on the CMM but perform correctly in assembly.
Offline CMM Programming: The Single Biggest Lead Time Lever
On-machine teaching, where the programmer drives the CMM manually to touch each feature point while the physical part sits on the machine table, is the traditional approach. It works. It is also the most expensive use of CMM machine time available to a quality department, and it occupies the machine during program development instead of during actual measurement.
Offline CMM programming develops the measurement routine entirely within a virtual simulation environment using the 3D CAD model of the part. The metrologist imports the CAD model, extracts the geometric features and GD&T callouts, defines probe paths, and validates the program including collision checking, before the physical part exists. When the first piece comes off the machine, the CMM program is already validated and ready to run.
What Offline Programming Actually Saves
The efficiency gain is not just in CMM machine availability. It is in parallel workflow execution. While the machinist is running the part, the CMM programmer is finalizing and validating the measurement routine. The two workflows run simultaneously instead of sequentially. For a precision aerospace component with a hundred or more characteristics, an on-machine teaching session can occupy the CMM for many hours. Offline programming compresses that time significantly because collision simulation catches probe path errors before they stop a live measurement run.
Software platforms commonly used for offline CMM programming, such as PC-DMIS and CALYPSO, allow the programmer to work with a digital twin of the specific CMM model, including the probe head and styli configuration. The simulation is not generic. It reflects the actual machine geometry, which means the validated program runs on the physical machine with minimal adjustment.
Pro tip: Keep your CMM programs version-controlled and tied to the drawing revision. When a drawing revision triggers a new FAIR, the previous CMM program becomes the starting point for the update rather than a rebuild. This is especially valuable for parts with stable geometry changes, where only a subset of characteristics are affected by the revision.
Common Mistakes That Cause FAIR Rejections
Most FAIR rejections are documentation failures, not measurement failures. The part is often in tolerance. The paperwork is not. Understanding the specific failure modes lets you build checkpoints that catch them before submission.
Missing Characteristics in Form 3
The most frequent Form 3 error is incomplete characteristic coverage. Title block callouts, general tolerance notes, and drawing notes (surface finish, material hardness requirements, identification marking) are characteristics that must appear on Form 3. Machinists and programmers tend to focus on dimensioned features and miss the notes section of the drawing. Every requirement on the drawing is a characteristic. If it appears on the drawing, it needs a balloon and a Form 3 entry with objective evidence.
CMM Labels That Do Not Match Balloons
When CMM output is imported into a FAIR package, the measurement labels in the CMM report must align with the balloon numbers on Form 3. If the CMM program uses its own internal feature naming convention (hole_01, bore_02, etc.) instead of the balloon numbers, the import creates a mapping problem that requires manual reconciliation. Build the CMM program using balloon numbers as feature identifiers from the beginning and this problem disappears.
Outdated Drawing Revisions
Inspecting and documenting against a drawing revision that has been superseded is a fundamental FAIR failure. It sounds obvious, and it still happens regularly on programs with multiple concurrent design activities. The ballooned drawing submitted with the FAIR package must match the current design revision on record. A pre-submission checklist that explicitly verifies drawing revision against the released design baseline catches this before it reaches the customer.
CMM Programming Approaches Compared
Approach
Lead Time Impact
Best Application
On-Machine Teaching (Manual)
Highest. CMM is occupied during program development. First article measurement cannot begin until programming is complete.
Simple parts with few features, one-off prototypes where reuse is unlikely, or shops without CAD-model-based programming capability.
Offline Programming with CAD Model
Lowest. Program development runs in parallel with machining. CMM is available for production inspection while the new program is being built.
Complex aerospace and precision components with high feature counts, repeat production parts requiring reusable programs, and any program where FAI cycle time directly affects delivery.
Hybrid: Offline Build, On-Machine Verification
Moderate. Offline work reduces teach time significantly. Short on-machine session validates and fine-tunes the program against the physical part.
Parts with casting or forging inputs where nominal-to-actual variation requires probe path adjustment, or programs where the CAD model has known deviations from the physical part geometry.
For precision machined components where full 3D CAD models are standard deliverables from the design process, offline programming is the correct default. The hybrid approach adds value specifically when incoming material variability creates a gap between the CAD model and the actual part geometry that the simulation environment cannot anticipate.
How SCPM's MetroLab Division Approaches FAI Programming
Summit City Precision Machining's MetroLab division handles CMM programming and inspection support as a defined service, not as an afterthought to the machining workflow. For customers requiring first article inspection documentation, the CMM program is developed against the customer's CAD model before the first part runs. That means when the part comes off the 5-axis CNC mill or the lathe, the measurement program is ready.
SCPM's A2LA accreditation means the measurement environment itself meets documented standards for calibration, environmental controls, and measurement uncertainty. For aerospace customers, that accreditation is not a marketing claim. It is the difference between an inspection result that an OEM quality team will accept and one they will question. The MetroLab cleanroom provides a controlled environment for dimensional inspection of sensitive components, which is particularly relevant for tight-tolerance aerospace parts where thermal variation would compromise measurement integrity.
PPAP documentation support is available alongside AS9102 FAIR packages. Many customers in the industrial and automotive tier supplier space require both. SCPM's ability to support both simultaneously, through the same team managing CMM programming and documentation, eliminates the coordination overhead that comes with using separate suppliers for machining and inspection services.
For customers evaluating aerospace inspection services in the Fort Wayne and broader Midwest industrial corridor, the combination of in-house machining capability, dedicated CMM programming resources, and A2LA accredited metrology means the FAI package is built by the same team that produced the part. That eliminates the translation loss that occurs when machining and inspection are separated across different facilities.
Pro tip: When requesting a quote for precision aerospace components that will require a FAIR, explicitly include the AS9102 documentation requirement in the initial RFQ. Suppliers who plan CMM programming into the original project schedule will deliver FAI packages in less time than those who treat inspection documentation as a parallel task to be assembled after machining is complete.
Frequently Asked Questions
What is the difference between a first article inspection and a routine incoming inspection?
A first article inspection is a one-time (or revision-triggered) qualification of the production process, not just the part. It demonstrates that your process, tooling, and documentation can repeatably produce a conforming part. Routine incoming inspection verifies individual lots against dimensional requirements without establishing that full process qualification. AS9102 FAIRs are required by aerospace and defense customers as proof of process capability at program launch.
Does AS9102 apply only to aerospace parts?
AS9102 was developed for the aerospace and defense supply chain, but its structure and rigor have been adopted more broadly. Some defense and industrial customers outside of traditional aerospace programs reference AS9102 or require equivalent FAI documentation. If your customer's purchase order references AS9102, the three-form FAIR structure applies regardless of the end application. Always check the contract rather than assuming the standard does or does not apply based on industry category alone.
How long does CMM programming take for a typical aerospace component?
Program development time scales with feature count and geometric complexity. A straightforward turned part with standard diameters, lengths, and a small number of GD&T callouts can be programmed offline in a few hours. A complex 5-axis milled aerospace structural component with compound-angle surfaces, deep pockets, and a high characteristic count can require multiple days of programming, simulation, and validation. Budgeting CMM programming time as a separate line item in project scheduling is the accurate approach.
What CMM software is compatible with AS9102 FAIR documentation?
CMM software does not produce AS9102 FAIRs directly. The CMM software produces measurement reports with feature results. Those results are then imported into FAIR documentation, either through dedicated inspection reporting software or through structured templates. The key requirement is that the CMM output can be imported with balloon-number-based feature labels that map directly to Form 3. PC-DMIS, CALYPSO, and similar platforms all support export formats compatible with this workflow when the CMM program is built with FAIR traceability in mind from the start.
When is a partial FAIR acceptable versus a full FAIR?
AS9102 allows partial FAIRs when a design change affects only a subset of characteristics. In those cases, only the changed characteristics and any characteristics that could be affected by the change require re-inspection and re-documentation. The customer's quality requirements and the specific contract language govern whether a partial FAIR is acceptable. Some customers require full re-inspection on any drawing revision. Confirm the requirement before assuming a partial re-inspection is sufficient.
Can CMM programming support both PPAP and AS9102 FAI on the same part?
Yes. The dimensional measurement data collected through a CMM program is objective evidence that serves both documentation systems. PPAP adds statistical process capability requirements (Cpk values for critical characteristics) and FMEA documentation that AS9102 does not require. The two systems address complementary but different quality requirements, and they cannot substitute for each other. A well-structured CMM program that captures all required characteristics with proper balloon-number labeling supports both packages from the same measurement data set.
Have you encountered a specific AS9102 FAIR documentation challenge or a CMM programming workflow that significantly changed your lead times? Share your experience below or reach out to the SCPM team directly.
References
Overview of AS9102 FAIR structure, forms, and characteristic accountability requirements
How CMM bottlenecks affect first article inspection lead times and methods to accelerate FAI
Offline CMM programming methodology and lead time benefits compared to on-machine teaching
Summary of AS9102 Rev C changes and alignment with AS9100 quality management requirements
Comments