First Article Inspection is the formal verification step that confirms a manufacturing process can consistently produce parts meeting all engineering requirements. In aerospace, this process determines whether a supplier’s production methods, tooling, and materials will deliver conforming hardware before committing to full-rate production or after a major change to design, process, or facility.The First Article…

First Article Inspection is the formal verification step that confirms a manufacturing process can consistently produce parts meeting all engineering requirements. In aerospace, this process determines whether a supplier’s production methods, tooling, and materials will deliver conforming hardware before committing to full-rate production or after a major change to design, process, or facility.
The First Article Inspection Report, commonly called the FAIR, serves as the documented evidence of this validation. It captures material certifications, dimensional measurements, special process approvals, and functional test results in a structured format aligned with AS9100-compliant quality management systems. For aerospace organizations, the FAIR is both a quality gate and a long-term traceability record.
This pillar guide from Connect 981 covers the complete FAI landscape: when first article inspection is required, how to execute the FAI process, what documentation AS9102 demands, how to maintain traceability across the supply chain, and how digital tools reduce FAI cycle time without sacrificing compliance.
First article inspection in aerospace is a formal, documented verification that the manufacturing process, tooling, methods, and suppliers can produce a part that conforms to all engineering, material, and functional requirements. The inspection evaluates a production-representative sample manufactured under normal production conditions, not a hand-finished prototype or engineering sample.
The critical distinction is that FAI evaluates the manufacturing system, not just a single part. The goal is to prove process capability and consistency before mass production begins. A successful FAI establishes the production baseline and becomes the reference for any future partial FAI or delta FAI activities.
Aerospace FAI is governed by SAE AS9102, with the latest revision (AS9102D) released in March 2024. This standard defines the documentation structure, required content, and acceptance criteria that suppliers must follow.
Key terms used throughout this guide:
Unlike routine in-process or final inspection, FAI is event-driven. It occurs at specific triggers such as new part introduction, major design changes, or supplier transitions. The inspection scope is exhaustive, covering 100% of drawing characteristics rather than statistical sampling.
First article inspection matters to aerospace regulators, primes, and certification bodies because it provides documented evidence that production processes meet design intent before hardware enters service. The FAI requirement flows from quality standards through purchase orders into contractual obligations.

The regulatory framework includes:
OEMs like Boeing, Airbus, Lockheed Martin, and Rolls-Royce flow down FAI requirements through purchase orders and quality clauses. These clauses typically reference AS9102 explicitly and may add customer-specific requirements for FAIR format, approval workflows, or delegated representative involvement.
FAI connects to multiple regulatory environments:
For organizations pursuing AS9100 certification, FAI records serve as evidence of process control and design understanding during audits. Auditors specifically verify linkage between the first build and ongoing production control plans.
In aerospace, FAI (AS9102) often integrates with Advanced Product Quality Planning per AS9145. The FAI serves as the production validation step in APQP Phase 4, demonstrating that the production process can meet design specifications and quality requirements.
Timing and triggers for FAI are defined by AS9102 and customer contracts. Understanding these triggers is essential for compliance and for avoiding rework when a FAIR is rejected for scope issues.
Typical triggers for a full FAI per AS9102 and common OEM practices:
Trigger
Description
New part number
First production of a new design or purchase from a new supplier
New supplier
First production by a supplier, regardless of prior part history
New facility
First production at a new manufacturing location
New methods/tooling
Adoption of manufacturing methods or tooling differing from approved baseline
Material changes
New raw material forms or supplier sources
Engineering design changes often require FAI. The extent depends on what changed:
Process change triggers include major changes in NC programs, process routing, manufacturing sequence, special processes (heat treat, plating, welding), or raw material specifications.
Many OEM supplier quality manuals mandate FAI after a production lapse of 24 months or more. This reflects concern that knowledge degradation, personnel turnover, and equipment drift during extended gaps may introduce undetected changes to process capability.
A separate cluster article on when FAI is required expands on these triggers with specific AS9102D clause references and OEM examples.
Readers often confuse first article inspection FAI with the Production Part Approval Process. Both serve as quality gates, but they differ in scope and origin.
PPAP originated in the automotive industry as part of the APQP framework. It covers a broad range of deliverables: process capability studies, measurement system analysis, control plans, and long-term production readiness documentation.
FAI (AS9102) focuses heavily on characteristic verification and traceability for a single build event. It validates that a manufacturing process can produce conforming parts but does not inherently require statistical capability studies or control plan submissions.
Key distinctions:
Aspect
FAI (AS9102)
PPAP
Primary focus
Characteristic verification, material/process traceability
Broad production readiness
Documentation
Three AS9102 forms plus attachments
Up to 18 elements including capability studies
Industry origin
Aerospace (IAQG)
Automotive (AIAG)
Scope
Single build event validation
Long-term production capability
FAI can be considered a subset of a full PPAP package. However, aerospace primes may require both AS9102 FAIR and additional PPAP or AS9145 deliverables for complex programs.
Common aerospace customer requirements include:
The cluster article FAI vs PPAP compares required documents line-by-line across both approval process frameworks.
The FAIR is the core deliverable of first article inspection. Unless a customer-specific template is mandated in the purchase order or supplier quality manual, the three AS9102 forms serve as the documentation standard.
The three forms work together to establish complete traceability:
Form
Name
Purpose
Form 1
Part Number Accountability
Identifies the part, revision, FAI type, and reason
Form 2
Product Accountability
Documents materials, special processes, and tests
Form 3
Characteristic Accountability
Records inspection results for every balloon
A ballooned drawing or 3D digital product definition identifies every characteristic with unique balloon IDs. These IDs map directly to line items on AS9102 Form 3, creating traceability between visual part definition and inspection results.
Common supporting documents attached to a FAIR package:
Key characteristics and critical-to-quality features must be explicitly identified using designators like “KC,” “CC,” or customer-specific markings. These designations signal which features warrant special controls during production.
Connect 981 can host digital FAIR templates aligned with AS9102D, auto-populate fields from ERP and MES data, capture ballooned drawing links, and enforce mandatory attachments before FAIR submission.
A dedicated cluster article on FAI documentation requirements walks through each field in AS9102 Forms 1–3 with completed examples.
Form 1 establishes the identity and context for the FAI. Required content includes:
Form 1 distinguishes between Detail FAI (single-component parts manufactured as a discrete unit) and Assembly FAI (multi-component assemblies with a bill of materials).
For assemblies, Form 1 must list:
This hierarchical approach ensures that if a sub component fails FAI or has a nonconformance, the impact on overall assembly acceptance is transparent and traceable.
Form 2 documents raw materials and special processes used to manufacture the first article.
Raw material entries include:
Special process entries include:
Process Type
Example Specification
Required Documentation
Anodizing
AMS2469, Type II or III
Process spec, supplier code, approval status
Passivation
AMS2700
NADCAP certification, lot number
Heat treatment
AMS specification with temp/time
Furnace certification, chart records
NDT
Customer or NADCAP spec
Operator certification, inspection report
Welding
AMS or customer spec
Filler material, heat input, post-weld treatment
Functional tests such as pressure tests, torque tests, or electrical continuity for harnesses are linked via procedure numbers and test report identifiers.
Example row for a machined strut fitting:
Material
Spec
Heat Lot
CoC Reference
7075-T651 Aluminum Plate
AMS-QQ-A-250/12
H-2024-0847
CoC-2024-0847-A
Form 3 is typically the most time-consuming element of FAIR preparation. Each line corresponds to a characteristic from the ballooned drawing.
Required fields for each characteristic:
Field
Description
Balloon number
Links to ballooned drawing
Drawing sheet and zone
Location reference for multi-sheet drawings
Characteristic description
“Bore OD,” “Thread M10x1.5,” “Flatness of seating surface”
Specification or tolerance
Nominal dimension with tolerance band
Key characteristic designator
KC, CC, or standard feature
Inspection method
CMM, micrometer, visual, functional test
Measured result
Actual numerical value or attribute result
Gage ID
Traceable to calibration records
Acceptance status
Accept, reject, or conditional
Characteristics are recorded as either attribute data (pass/fail for thread presence) or variable data (numerical measurement for bore diameter). Using the correct data type ensures accuracy and supports process control.
Inspection methods may include CMM, hand tools (micrometers, calipers), optical comparators, calibrated tools, or automated scanning equipment. Gage ID and calibration state must be traceable to ISO 17025 labs where applicable.
Manual Form 3 population using spreadsheets is error-prone. Connect 981 can ingest CMM output files and auto-fill inspection results linked to balloon IDs, reducing transcription errors and preparation time.
Material and dimensional integrity together determine whether the first article is acceptable and reliable in service. Both require rigorous documentation.

Raw material record requirements:
Aerospace-specific scenarios demand heightened traceability. Titanium forgings for engine mounts require heat lot documentation linking specific material to the first article serial number. Composite prepreg materials have shelf-life limitations requiring lot tracking to ensure out-of-life material is not incorporated.
Dimensional record requirements:
Common measurement tools in aerospace FAI:
Tool Type
Application
CMM
Complex geometry, GD&T features, high-precision dimensions
Portable arms
Large parts, field measurements
Laser scanners
Complex surfaces, rapid data capture
Pin gages
Go/no-go verification of holes
Thread gages
Pitch and major diameter verification
Hardness testers
Material property verification per spec
Dimensional records must include gage IDs and calibration due dates. Inadequate metrology control is a frequent audit finding. A gage out of calibration at time of measurement can invalidate FAI results for that characteristic.
The cluster article on FAI traceability explores how raw material, process, and dimensional records tie into serialized part histories over an aircraft’s service life.
The FAI workflow spans multiple functions and requires coordination between quality, manufacturing engineering, supply chain, and the customer. Understanding the operational sequence reduces cycle time and prevents rework.
Planning phase activities:
Manufacturing engineering planning:
The first article must be manufactured under normal production conditions using approved programs, fixtures, materials, and qualified personnel. FAI performed on engineering samples or under special lab conditions does not validate the actual production process.
Inspection and documentation execution:
Review and approval sequence:
Connect 981 orchestrates this workflow end-to-end, from digital traveler creation and step-by-step work instructions to automated FAIR compilation and customer portal submission.
This sequential checklist reflects what quality and manufacturing engineers execute during a complete FAI:
Coordination touchpoints occur at planning (scope agreement), mid-build (observation of critical steps), and review (internal verification before customer submission). Any nonconformances discovered during FAI must be documented with corrective actions, even if the FAIR is approved with concessions.
Delta and partial FAIs avoid redoing a full first article inspection when only limited changes have occurred. Both maintain compliance while reducing redundant work.
Partial FAI focuses only on characteristics affected by a change. For example, if drawing Rev B changes only two bore diameters and a tapped hole position, the partial FAI measures only those three features while referencing the prior full FAIR for unchanged characteristics.
Delta FAI is a customer- or OEM-defined variation used when:
Documentation expectations for both types:
Requirement
Partial FAI
Delta FAI
FAIR type statement
“Partial” clearly stated
“Delta” per OEM definition
Original FAIR reference
Required
Required
Scope definition
Changed characteristics only
Facility/equipment changes
Supporting evidence
Process documentation for changes
Equipment qualification records
Concrete example: Moving a machining operation from Plant A to Plant B in 2027 would trigger a delta FAI capturing facility-related changes while referencing the original FAIR from the initial production baseline.
Connect 981 versions FAIRs, tracks lineage between full and partial/delta FAIs, and presents a clear audit trail for regulators and customers.
FAI failures often stem from preventable documentation and process errors rather than fundamental manufacturing problems. Understanding these risks helps organizations avoid costly errors and customer rejections.
Documentation issues:
Metrology and data errors:
Process-related problems:
Communication gaps:
The cluster article on common FAI errors presents a detailed checklist of avoidable mistakes and detection methods before customer submission.
Platforms like Connect 981 reduce these errors through enforced templates, automated data import from CMM systems, validation checks before submission, and a single source of truth for drawing revisions.
Traceability is central to aerospace safety cases and explains why FAI is so documentation-intensive. The FAIR creates an unbroken chain connecting manufactured parts to their materials, processes, and verification records.
FAI records connect:
This chain enables rapid investigation when field issues occur. If a component fails in service, investigators can trace backward from the serial number to the FAI, then to the specific material heat lot, special process vendor, and dimensional verification records.
Typical retention expectations:
Context
Retention Period
Commercial aerospace
10+ years, often through aircraft service life (20-40 years)
Defense contracts
Program life or indefinite per contract requirements
Safety-critical components
Through product lifecycle plus investigation window
Rapid retrieval capability matters for regulatory audits, customer investigations, and accident analysis. Older revisions and superseded FAIRs must remain accessible even after design updates.
The risk of scattered PDFs and spreadsheets across network drives creates compliance exposure. Multi-site operations often struggle with FAIR location and version control, particularly after personnel turnover or facility acquisitions.
Connect 981 centralizes FAIR data, links it to work orders and serial numbers, and provides controlled access to OEMs and tiered suppliers via a shared digital layer.
The cluster article on FAI traceability deep-dives into serial number management, lot tracking, and integration with ERP, MES, and QMS systems.
The aerospace industry is transitioning from paper-based FAIs and standalone spreadsheets toward integrated digital workflows. This shift addresses longstanding pain points while maintaining stringent requirements.

Common manual pain points:
Digital FAI capabilities:
Integration with MES, ERP, and QMS provides shared part master data, process routings, nonconformance linkage, and document control. This reduces duplication and ensures accuracy between systems.
Connect 981 serves as a unified operations platform that:
In aerospace MRO environments, digital FAI systems verify first article repairs or modifications, document new repair procedures, and integrate with maintenance records for product reliability traceability.
The cluster article on digital travelers and FAI focuses on how digital work instructions and FAIRs work together on a connected shopfloor.
Emerging AI and analytics capabilities augment FAI workflows while keeping domain experts in control.
AI-assisted characteristic extraction from CAD models and engineering drawings reduces manual ballooning time. Machine learning models trained on aerospace drawings can identify features, extract dimensions and tolerances, and propose balloon numbering schemes aligned with customer conventions.
Advanced analytics on FAIR data across programs and suppliers identifies systemic issues:
Connect 981 uses AI-assisted root cause analysis to highlight high-risk features before they fail in FAI or production. Predictive insights flag characteristics similar to historical problem areas for additional review.
AI augments but does not replace domain experts. Quality engineers, metrologists, and manufacturing engineers retain judgment over design changes, process controls, and supplier qualification decisions.
FAIs often sit on the critical path for program launches and design changes. A program awaiting FAI approval cannot begin full production run, which delays revenue and may incur customer penalties.
Typical drivers of long FAI cycle times:
Best practices for acceleration:
Practice
Impact
Early planning and scope confirmation
Prevents rework from unclear requirements
Pre-approved templates and conventions
Reduces formatting questions
Concurrent inspection planning
Eliminates metrology scheduling delays
Digital data capture at point of use
Eliminates transcription errors
Integrated FAIR generation
Cuts preparation time by 75%+
Digital tools cut FAI turnaround through automated data capture, single-click FAIR generation, integrated approvals, and shared visibility for OEMs and suppliers. Organizations report reducing FAI preparation from 16 hours to 4 hours per part using automated approaches.
The cluster article on reducing FAI cycle time offers quantitative examples and case scenarios demonstrating specific acceleration strategies.
Defense, space, and safety-critical systems often add requirements beyond standard AS9102 FAI. Understanding these additions prevents compliance gaps on regulated programs.
Defense-specific FAI requirements:
Some defense contracts tie FAI approval to program risk reviews. If the FAI reveals unexpected manufacturing challenges, program risk posture escalates, triggering additional oversight.
ITAR and export control implications:
FAI data including drawings, 3D models, and FAIRs may be controlled technical data under ITAR or EAR. This means:
Connect 981’s shared yet permissioned environment supports collaborative FAIs on defense programs while respecting data segregation. Access controls, encryption, and user authentication prevent unauthorized access to controlled FAI data.
The cluster article on FAI in defense contracts addresses these topics with detailed examples including common clauses and flow-down language.
First article inspection will evolve significantly over the next 5–10 years as model-based definition and automated metrology become standard across the aerospace industry.

Model-Based Definition (MBD) and Digital Product Definition:
MBD embeds all design intent, tolerances, and annotations in 3D CAD models. This enables:
Automated metrology trends:
Digital thread integration:
FAI data will increasingly connect to PLM, ERP, MES, QMS, and fleet maintenance systems. This enables:
Platforms like Connect 981 serve as the connective layer between these systems, enabling standardized FAI workflows across global factories and multi-tier supplier networks. Industry standardization of digital FAIR data exchange will reduce proprietary silos and enable easier OEM-supplier collaboration.
The future state is a scenario where suppliers receive design specifications, automatically generate FAI plans, manufacture with digital work instructions, compile FAIRs from CMM data and material certifications, submit via digital portal, and receive approval within days rather than weeks.
Organizations that standardize FAI workflows reduce cycle time, cut costly errors, and maintain customer confidence through audit-ready documentation. The path forward requires evaluating current FAI maturity, identifying manual bottlenecks, and adopting digital tools that integrate with existing systems.
Connect 981 enables aerospace manufacturers and suppliers to modernize their FAI process without replacing ERP or MES infrastructure. Request a demo to see how digital FAI workflows can work for your next project.
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.