AS9102 first article inspection depends on three core forms: Form 1, Form 2, and Form 3. Together, these AS9102 forms document what article was inspected, what materials and processes were used, and whether every required design characteristic was verified.This article explains what each form is for, what evidence belongs with it, and where aerospace suppliers…

AS9102 first article inspection depends on three core forms: Form 1, Form 2, and Form 3. Together, these AS9102 forms document what article was inspected, what materials and processes were used, and whether every required design characteristic was verified.
This article explains what each form is for, what evidence belongs with it, and where aerospace suppliers usually make mistakes that lead to FAIR rejection, rework, or delayed customer approval. The focus is AS9102C, the current version of the AS9102 standard, which was released on June 28, 2023.
A first article inspection is a production part verification process that ensures products meet design specifications and requirements before full-scale production begins. A first article inspection report, often called a FAIR, is the documented report package that shows the work was completed and the requirements were met. In practical terms, the three AS9102 forms and their attachments become the first article inspection fai package submitted to an OEM, Tier-1 customer, or regulated MRO customer.
AS9102 was developed by the International Aerospace Quality Group (IAQG) and is published by SAE International. The standard establishes a consistent, globally recognized framework in the aerospace and defense industries for conducting a First Article Inspection (FAI). Connect 981 supports this work by digitizing AS9102 workflows, but this guide is primarily educational: it is written for suppliers that need to get the documentation right the first time.

In aerospace, quality assurance forms serve as a roadmap and birth certificate for manufactured parts, offering critical quality assurance benefits. AS9102 forms also ensure supply chain traceability, traveling with parts to allow investigation of failures by linking them to materials and manufacturing processes used.
Form 1 documents what article is being inspected in the first article inspection. That article may be a detail part, an assembly, or a subassembly. Form 1 ties the FAIR to specific part numbers, drawing revisions, model definitions, customer purchase orders, and related lower-level inspections.
Form 1 is the cover sheet of the article inspection report. OEM quality teams and auditors use it to quickly understand what the first article inspection report covers and how the inspected article relates to the engineering definition. If Form 1 is wrong, the customer may not trust the rest of the report.
AS9102C, released on June 28, 2023, is the current version. AS9102B was released on October 6, 2014, and AS9102A was released on January 13, 2004. Current submissions should follow the C layout when AS9102C is required, although legacy FAIRs may still exist in older AS9102A or AS9102B formats.
Typical Form 1 data includes:
Form 1 item
What it controls
Part number and part name
Confirms the article being inspected
Drawing number and drawing revision level
Connects the FAIR to the engineering definition
FAI report number or FAIR identifier
Provides a unique tracking reference
FAI type
Identifies full FAI, partial FAI, or re-inspection scope
Organization name and CAGE code
Identifies the supplier organization
Purchase order number
Links the inspection to the customer contract
FAI completion date
Shows when the inspection was completed
Reviewed and approved fields
Records the responsible person or people for FAIR approval
Nonconformance indication
Identifies whether documented nonconformances are included
Form 1 of AS9102 requires identification of the part and associated sub-assemblies, while Form 2 must account for all material and process specifications, including any special processes and functional testing defined as design requirements. For assemblies, Form 1 should identify the higher-level assembly and list the associated sub assemblies or lower-level parts. If those sub-assemblies have their own first article inspection fai submitted separately, the related FAIR identifiers should be listed or referenced.
Evidence that belongs with Form 1 includes:
Common Form 1 mistakes include:
In practice, many of these errors are transcription problems. A digital platform like Connect 981 can reduce the risk by auto-populating Form 1 from ERP, MES, and PLM data. The useful control is simple: part number, revision, PO, and drawing information should come from governed source systems rather than being typed repeatedly into spreadsheets.
Form 2 documents the article’s material specifications, special processes, finishes, and functional tests. This is often where aerospace suppliers run into the most documentation gaps because the evidence may come from mills, distributors, outside processors, internal test teams, or customer-furnished material records.
Product accountability means proving that all required material, process, and functional test requirements in the drawing, model, specifications, and customer contract have been correctly applied and verified. The form is not just a list of suppliers. It is the bridge between engineering requirements and the actual materials and processes used to produce the article.
Key Form 2 categories usually include:
Evidence that belongs with Form 2 includes:
Category
Evidence to attach or reference
Raw materials
Mill certificate or distributor certificate with heat or lot number matching the part or batch
Special processes
Certificate of Conformance, process results, processor name, approval status, and exact specification revision
Functional testing
Test report or results summary tied directly to the FAI unit or lot
Test equipment
Calibration certificate where equipment status must be verified
Customer-furnished material
Records showing receipt, identity, and use of the furnished material
A common example is plating. If the drawing requires a specific plating specification and revision, the Form 2 entry should reference the exact specification and the supplier certificate should show the same requirement. A generic note such as “per customer spec” is not enough. If the drawing requires AMS 2411 Rev E and the certificate references AMS 2411 Rev C, the customer will likely reject the FAIR or require clarification.
AS9102C removed the signature field on Form 2 that existed in AS9102B. One of the significant changes from AS9102B to AS9102C includes the removal of the signature field in Form 2 and Form 3, which has been renumbered as a result. Overall review and approval are handled through the designated approval fields, primarily on Form 1.
Common Form 2 mistakes include:
Build-to-print parts usually have direct drawing and specification callouts that drive Form 2. Build-to-spec work and repair or overhaul work can be more layered. In MRO environments, Form 2 may need to reflect OEM requirements, maintenance manual requirements, repair scheme requirements, and customer-specific instructions. The constraint is not only whether the process was performed. The supplier must show that the correct requirement was identified and verified.
A connected operations layer like Connect 981 can centralize material certs, special process CofCs, and test reports. That makes Form 2 population faster, but more importantly, it makes audit retrieval practical when a customer asks for evidence months or years later.

Form 3 is where every design characteristic is listed, ballooned, and matched to actual inspection results for the first article. It is the most detailed part of the first article inspection report and the place where customers often spend the most review time.
Form 3 of AS9102 mandates that all product characteristics, such as dimensions and tolerances, must be documented, and an inspection drawing or model is required to clearly identify these characteristics with uniquely numbered inspection balloons. This includes dimensions, GD&T, datum references, drawing notes, finish callouts, marking requirements, thread requirements, and other characteristics defined by the engineering package.
Suppliers typically use ballooned drawings or annotated 3D models:
Typical Form 3 row content includes:
Form 3 row item
Purpose
Characteristic number
Ties the row to the ballooned drawing or model
Reference location
Identifies sheet, zone, view, section, model element, or PMI feature
Requirement
Records dimension, tolerance, GD&T symbol, finish, or note
Nominal and tolerance limits
Defines the acceptance range
Result
Shows actual measured value or verified test outcome
Inspection method
Identifies CMM, calipers, thread gage, go/no-go gage, visual inspection, or test method
Nonconformance field
Indicates whether the result failed and links to disposition
Additional data or comments
Provides needed clarification without replacing objective results
The discipline here is coverage. “All characteristics” means more than major dimensions. It includes critical notes, general tolerance requirements, special marking, surface finish, thread callouts, sealant notes, and requirements embedded in digital product definition.
AS9102C removed the per-form signature column from Form 3 as well. The standard now emphasizes clear recording of inspection results and dispositions rather than multiple signature blocks on every form. The signature and approval control is consolidated through the required FAIR review and approval process.
Common Form 3 mistakes include:
AS9102C emphasizes the inclusion of verification against digital specifications, such as multi-dimensional CAD files, which was a notable advancement in the standard. For model-based definition, verification evidence may include CMM programs referencing the 3D model, PMI-linked inspection plans, digital clearance checks, or software-based tolerance analysis. The evidence can be digital, but it still must be traceable to each recorded characteristic on Form 3.
Connect 981 can link Form 3 rows directly to inspection plans, in-process checks, CMM output, and defect records. The value is not only fewer keystrokes. The value is maintaining a controlled audit trail from the ballooned requirement to the actual result and any nonconformance disposition.

A complete first article inspection report includes all three AS9102 forms plus supporting evidence: drawings, models, certs, test reports, calibration records when applicable, and nonconformance records. The report should show that the production run used to create the FAI article was controlled, understood, and capable.
An AS9102 First Article Inspection Report (FAIR) ensures that the production process is stable, repeatable, and capable of conforming to strict safety standards. It is not required for every batch. AS9102 FAIRs are triggered by new parts, design changes, process shifts, new suppliers, or extended inactivity of a part.
The logical flow is straightforward:
Each AS9102 form contains universal identifiers for traceability, repeated across forms to facilitate tracking of inspections. These identifiers typically include part number, FAIR identifier, drawing revision, organization data, and other control information that allows the customer to connect the forms into one coherent package.
This structure supports AS9100D Clause 8.5.1.3 on production process verification. AS9102 first article inspection provides a standardized way to demonstrate that the manufacturing process can produce conforming parts across the aviation, space, and defense supply chain.
Aerospace customers use the article inspection report to establish baseline capability, approve suppliers for ongoing production, and support future audits or investigations. When a field issue occurs, the FAIR helps quality and engineering teams trace the article back to its drawings, materials, process certificates, inspection results, and any disposition records.
Digital traceability across all three forms is increasingly expected, especially when organizations work with multi-dimensional CAD models, complex assemblies, and supplier tiers spread across multiple companies. Connect 981 can act as a unified layer between ERP, MES, QMS, PLM, and supplier systems so the data needed for all three forms is consistent, up to date, and available without hunting through emails and shared folders.
Many FAIRs are rejected not because the parts are bad, but because the documentation is incomplete, inconsistent, or not aligned with AS9102C expectations. The product may meet the requirement, but if the evidence is weak, the customer still has a problem.
FAI is typically required when there is a change in design, production process, or when a new supplier is introduced, ensuring that all aspects of the production process are verified. A new or revised part, a tooling change, a process relocation, or a long production gap can all trigger the need to conduct a full or partial FAI before the part moves into full production.
Common rejection themes include:
The impact is predictable: repeated customer feedback loops, additional review time for quality engineers, delayed release into the first production run or ongoing production run, and avoidable pressure on program schedules.
Standardized templates, training, and digital workflows reduce this risk. The goal is not to make the paperwork prettier. The goal is to ensure every required field is completed, every attachment is present, every revision is current, and every result is traceable before submission.
A typical aerospace supplier moving from spreadsheet-based FAIRs to a digital article inspection workflow can use Connect 981 to enforce required fields, compare drawing revision data against ERP and PLM, flag missing certificates, and check that Form 3 balloon counts match recorded rows before the FAIR goes to the customer.
The form-by-form discipline matters, but the larger operational problem is data continuity. Aerospace suppliers often manage FAIR evidence across ERP records, MES travelers, QMS nonconformance logs, supplier emails, shared folders, CMM files, and paper inspection sheets. That fragmentation creates risk.
Connect 981 is built as an aerospace operations platform for connected shopfloor execution, supplier collaboration, and compliance-ready documentation. For AS9102 forms, the platform supports:
For operations leaders, manufacturing engineers, quality managers, and supply chain teams, the outcome is practical:
Connect 981 can be used for both production FAIs and MRO-related first article inspections when new repair routes, repairs, or modifications are introduced. The platform’s low- and zero-code workflow builder lets teams adapt AS9102 templates for customer-specific FAIR formats without relying on heavy custom IT projects.

To see how this works in practice, request a demo of Connect 981 and review a live digital AS9102 first article inspection workflow from drawing ballooning through FAIR submission.
This article focused on the three AS9102 forms and the documentation mistakes that commonly create rework. Teams that need broader guidance should also review when FAI is required, how full and partial FAI decisions are made, and what re-inspection triggers apply after a change.
Useful next resources:
Mastering as9102 forms turns first article inspection from a paperwork burden into a repeatable process. With clear documentation, disciplined revision control, and the right digital workflow, suppliers can provide better evidence, reduce customer rework, and support quality and on-time delivery.
Whether you're managing 1 site or 100, Connect 981 adapts to your environment and scales with your needs—without the complexity of traditional systems.