When First Article Inspection Is Required in Aerospace Manufacturing

First article inspection is not a one-time paperwork exercise. In aerospace manufacturing, it is an event-driven verification step used to confirm that a production process can make conforming hardware under controlled, repeatable conditions. That means the real question is not only what an FAI contains, but when it becomes mandatory.

Under AS9102 and common aerospace customer flowdowns, FAI requirements are triggered by specific changes to design, production, sourcing, location, tooling, materials, or continuity of manufacture. The compliance risk comes from missing those trigger events or applying the wrong scope. Teams often overreact by launching a full FAI when a partial update would satisfy requirements, or underreact by treating a meaningful process change as routine production. For a broader overview of AS9102 first article inspection in aerospace operations, start with the hub guide; this article focuses specifically on trigger logic and decision rules.

The operational objective is straightforward: translate standard language and customer clauses into internal rules that engineering, quality, supplier management, and production can apply consistently. Done well, that avoids unnecessary rebuilds while preserving compliance evidence for audits and customer review.

Regulatory and Contractual Foundations for FAI Requirements

How AS9100 and AS9102 Define Production Process Verification

In aerospace quality systems, FAI exists to verify production process capability against design requirements. AS9100 establishes the expectation for production process verification, while AS9102 defines the structured method for documenting that verification. The core principle is that the inspected item must be built using production-representative processes, not special handling that hides normal variation.

That distinction matters because FAI is intended to validate the manufacturing system as executed in the factory. If the routing, tools, programming, suppliers, or special processes differ from the approved production baseline, the earlier FAI may no longer be sufficient evidence.

Typical OEM Quality Clauses That Trigger FAI

AS9102 provides the baseline, but aerospace OEMs and upper-tier suppliers frequently add contract-specific triggers. Common examples include mandatory FAI on first shipment from a new source, after transfer to another site, after significant NC program changes, or after an extended lapse in production. Some customers also define different expectations for partial versus delta FAI, or require formal approval before shipment resumes.

Because of that, no team should rely on a generic checklist alone. The controlling requirement is usually the combination of AS9102, the purchase order, quality clauses, statement of work, and any supplier quality manual referenced by contract.

Linking FAI Requirements to Purchase Orders and Statements of Work

In practice, many FAI failures are contractual interpretation failures. Engineering may view a drawing revision as minor, while supplier quality sees a flowed-down clause requiring FAI on any revision change. The safest operating model is to connect part numbers, revisions, customer clauses, and site-of-manufacture data in the same decision path.

That is why mature organizations build FAI trigger reviews directly into contract review, engineering change control, and supplier onboarding. If the trigger is only checked at the time of shipment, the FAIR becomes a late discovery rather than a planned quality activity.

Standard Triggers for Full First Article Inspection

New Part Introduction and New Part Numbers

A full FAI is typically required the first time a new part number is produced. This is the most straightforward trigger because there is no approved production baseline yet. The FAIR establishes the initial evidence that all drawing characteristics, material requirements, special processes, and functional requirements have been addressed.

Even when a new part appears similar to an existing design, a new part number usually means a new accountability package. Similar geometry or shared routings do not eliminate the need for first-time verification unless the customer explicitly allows a reduced approach.

New Supplier or New Manufacturing Location

Changing who makes the part, or where the part is made, is another common trigger for a full or customer-directed FAI. A new supplier introduces different personnel, equipment, process controls, calibration environments, and sub-tier relationships. Likewise, moving the work to a new facility changes the production context even if the process plan appears unchanged on paper.

For aerospace programs, location matters because approvals often attach to the actual site performing the work. A supplier cannot assume that an approved FAI from Plant A automatically covers production at Plant B.

Major Changes in Methods, Tooling, or Materials

Significant process changes can invalidate the original production verification basis. Examples include replacing dedicated tooling with new fixtures, changing machining strategy in a way that affects feature generation, introducing a new raw material source or form, or altering the sequence of special processes. If the change can affect fit, form, function, reliability, or characteristic achievement, the FAI scope must be reassessed.

A useful rule is to ask whether the process that produced the last accepted FAI item is materially the same process being used now. If the answer is no, the organization should evaluate whether the change justifies a full FAI or a narrower update.

When Engineering Changes Require FAI: Full vs Partial

Assessing Design Changes by Characteristic Impact

Not every engineering change requires a new full FAI. The practical decision point is impact. If a revision changes only a limited set of characteristics, and the rest of the validated manufacturing baseline remains unchanged, a partial FAI is often the appropriate response. The updated FAIR package should show only the affected characteristics and preserve traceability to the original approved FAI for unchanged requirements.

For example, if a drawing revision changes two hole diameters and adds a tighter positional tolerance on one pattern, quality can often perform a partial FAI targeted to those affected characteristics and any upstream features influenced by the revised manufacturing method. A complete restart of all characteristic accountability may not be necessary.

Mapping ECNs and Drawing Revisions to FAI Scope

Engineering change notices should never flow into production without an FAI impact review. The review should answer three questions: which characteristics changed, which manufacturing steps are affected, and whether the change alters the validated process baseline. This creates a repeatable bridge between configuration control and AS9102 execution.

A revision letter by itself is not enough to determine scope. Some revision changes are administrative and do not affect product realization. Others may change geometry, material callouts, processing notes, source control requirements, or inspection methods. The decision must be based on technical effect, plus any customer instruction that makes all revisions FAI-relevant.

Examples of When a Partial FAI Is Sufficient

A partial FAI is commonly sufficient when the change is bounded and the unaffected portions of the process remain under the same validated conditions. Examples include:

• a revised chamfer dimension on a non-interface edge
• a changed hole size produced in an existing machining setup
• an updated material specification with equivalent form, processing, and downstream behavior, where customer requirements allow partial revalidation
• a drawing correction that changes characteristic numbering or note clarity without altering product definition, if documentation updates are still required

The key is disciplined justification. The FAIR should clearly show why the scope was partial, which characteristics were included, and what prior approved baseline supports the rest.

Delta FAI Scenarios in Aerospace Supply Chains

Facility Transfers and Equipment Changes

Delta FAI is often used when the part configuration remains the same but some element of the production environment changes. Common examples include moving work to another building, transferring a machine or fixture, replacing equipment with functionally equivalent equipment, or updating software or NC code in a way that may affect characteristic achievement.

Whether every equipment move triggers delta FAI depends on customer requirements and the significance of the change. A like-for-like machine replacement under controlled validation may support a narrow delta scope. A move that changes setup behavior, inspection method, environmental conditions, or operator sequence may require broader re-verification.

Program Lapses and Restart After Inactivity

Many aerospace contracts treat extended production gaps as an FAI trigger. The reason is operational rather than theoretical: after a long lapse, personnel may change, tooling may degrade, programs may be revised, suppliers may shift, and tribal knowledge may be lost. Even if the drawing has not changed, the manufacturing system may no longer match the one originally verified.

The exact inactivity period varies by customer, but quality teams should define internal review points well before a contractual threshold is reached. If a part has been dormant for an extended period, restart planning should include confirmation of tooling status, gauge availability, process approvals, source continuity, and whether a delta or full FAI is necessary.

OEM-Specific Definitions of Delta FAI Scope

One of the biggest sources of confusion is that not every customer uses delta FAI terminology in the same way. Some treat delta FAI as a practical subset of partial FAI. Others use it specifically for manufacturing location or process-environment changes. Still others require customer notification before any reduced-scope approach is accepted.

That is why internal procedures should never define delta FAI in isolation from customer flowdowns. The standard gives structure, but the contractual interpretation determines what evidence will be accepted.

Building an Internal FAI Trigger Matrix

Aligning Engineering Change Control with FAI Rules

The most effective way to avoid missed triggers is to build a formal trigger matrix tied to change control. Each event type should have a default response: no FAI, partial FAI, delta FAI, full FAI, or escalation for customer disposition. Event types usually include drawing revision changes, material substitutions, process routing changes, new tooling, machine replacement, source change, facility transfer, special process source change, and restart after inactivity.

This matrix should sit inside the engineering and manufacturing workflow, not outside it. If an ECN can be released without an FAI decision, the process is relying on memory rather than control.

Coordinating with Supply Chain and Supplier Quality

Many trigger events originate outside the engineering group. Purchasing may approve a new sub-tier source. Operations may shift work to another line. Supplier quality may authorize a facility transfer. Without shared visibility, a required FAI can be missed even when each team believes it is following procedure.

That is why aerospace organizations increasingly connect ERP, MES, quality systems, and supplier management records. Trigger logic becomes much more reliable when part revision, approved source, work center, routing, and special process approvals can be checked together.

Documenting Decisions and Justifications for Audits

Auditors and customers often ask a simple question: why was this level of FAI performed, or why was no new FAI performed after the change? The answer should not depend on verbal explanation. It should exist as a documented decision record linked to the part, revision, event, and approver.

Good documentation includes the trigger event, risk assessment, affected characteristics, customer clause review, disposition decision, and reference to prior FAIRs where applicable. This is especially important when the team decides that a full FAI is not required. Reduced scope is often acceptable, but only when the rationale is traceable and technically sound.

Using Connect 981 to Detect and Manage FAI Triggers

Automated Detection of Trigger Events from ERP/MES Data

In a digital aerospace environment, many FAI triggers can be detected from system events rather than manual review alone. Revision changes in PLM, supplier changes in ERP, routing updates in MES, machine reassignment, special process source changes, and work-order restart after long dormancy can all be surfaced as potential trigger conditions.

This matters because the risk is usually not misunderstanding AS9102 language. The risk is missing the fact that a change happened somewhere else in the production data chain. Automated detection helps quality teams review candidate events before parts reach shipment.

Configurable Rules for Full, Partial, and Delta FAI

Different aerospace programs require different decision rules. A defense contract may require stricter restart logic than a commercial program. One customer may allow a partial FAI for a bounded design change, while another may insist on a broader re-submission. Digital rule configuration allows those differences to be applied consistently without maintaining disconnected spreadsheets or tribal interpretations.

At the operational level, the goal is not to automate judgment away. It is to route the right events to the right reviewers with the right baseline data so the FAI decision is fast, repeatable, and defensible.

Audit Trails for Why a Particular FAI Was or Was Not Performed

For regulated manufacturing, the most valuable output is often the decision trail. If a program team decides that moving production to a validated equivalent machine required only delta verification of selected characteristics, that logic should be captured alongside the supporting records. If a revision change was administrative only, that conclusion should also be documented.

Connect 981-style digital traceability supports this by linking trigger events, approvals, affected part records, and FAIR documentation in a single audit path. That makes internal review easier and reduces friction when customers or auditors ask how the organization determined FAI scope.

Ultimately, determining when first article inspection is required in aerospace comes down to disciplined event recognition. New part introduction, source or location changes, major process changes, engineering revisions, and restart after inactivity all deserve structured evaluation. The strongest organizations do not treat FAI as a late-stage form package; they treat it as a controlled response to production change.