Teams should choose full FAI when there is no valid prior baseline for the current part configuration and production method. Partial FAI is appropriate only when an existing FAI remains valid and the team can clearly define which characteristics, operations, materials, tools, or sources were affected by a change.

In a partial FAI, unchanged characteristics are usually not remeasured if a documented impact assessment shows they were not affected by the change. They should still be traceable to a prior accepted FAI, with clear references, rationale, and customer-specific requirements checked before relying on carry-forward evidence.

A production lapse commonly triggers FAI re-evaluation at the AS9102 or customer-defined threshold, often two years. It does not always require a full FAI; partial FAI may be acceptable if the prior baseline, revision, process, tooling, source, and evidence remain valid.

The organization performing the first article inspection is normally responsible for completing the AS9102 forms. In practice, quality coordinates the package, but engineering, manufacturing, inspection, purchasing, and suppliers may all provide controlled inputs. Final accountability depends on contract flowdown and approved procedures.

FAI automation is most useful for repetitive, traceability-heavy work: characteristic extraction, ballooning, AS9102 form population, evidence collection, completeness checks, revision impact analysis, and approval routing. It still requires qualified review for interpretation, acceptance decisions, and nonconformance handling.

A tooling change usually requires a partial FAI when the changed tool can affect one or more design characteristics, the manufacturing or inspection method, or the evidence used to show conformance. Routine like-for-like maintenance may not trigger it, but the rationale should be documented under change control.

A manufacturing process change triggers a new or partial FAI when it could affect product characteristics, fit, form, function, or the validity of the original FAI evidence. Not every routing edit or administrative change requires a new FAI, but the decision should be controlled, documented, and customer-aware.

An AS9102 FAI requires objective, traceable evidence that the first production article was built and inspected against the released design record and contract requirements. The usual package includes AS9102 Forms 1, 2, and 3, plus supporting records such as ballooned drawings, measurement results, material and process certifications, test records, and approved nonconformance dispositions where applicable.

There is no universal fixed interval for internal FAI audits. Most regulated manufacturers use a risk-based cadence: self-check critical FAIRs before submission, sample completed FAIRs periodically, and re-audit after design, process, supplier, tooling, system, or customer requirement changes.

Aerospace manufacturers prove FAI trigger handling by maintaining traceable evidence from engineering change, planning, production, inspection, and quality records. The proof depends on controlled trigger rules, linked records, audit trails, and disciplined change control; software alone does not guarantee completeness.

Out-of-tolerance results during FAI are normally treated as nonconformances, not as paperwork issues. The part is contained, the measurement is verified, the result is recorded, and disposition follows the approved quality process, often involving MRB, engineering, and customer notification when required.

There is no universal FAI cycle time target for complex aerospace assemblies. For mature programs, 5–15 business days from first article build completion to an internally reviewed FAIR may be realistic if data, inspection capacity, supplier evidence, and revisions are ready. New or unstable assemblies often take weeks longer.

A pre-submission FAI checklist should confirm that the FAIR is complete, internally consistent, and backed by objective evidence before customer submission. It should cover AS9102 forms, revision alignment, characteristic accountability, measurement results, material and process traceability, nonconformances, approvals, and customer-specific rules. It does not guarantee acceptance.

Digital travelers reduce missed FAI steps by controlling sequence, requiring data capture, surfacing current revision requirements, and creating electronic evidence. They do not fix weak routings, poor characteristic planning, or disconnected MES, PLM, ERP, and QMS data without validation and change control.

Decide based on the scope and risk of what changed, not just whether an ECO exists. If the change can affect fit, form, function, manufacturability, inspection results, tooling, software, source, or process capability, reassess FAI scope. Partial FAI is common for localized changes, but a full FAI may be necessary when the impact is broad, uncertain, or poorly traceable.

No. Aerospace parts do not automatically require FAI just because they are used on an aircraft or defense program. FAI is usually driven by customer flowdowns, AS9102 requirements, AS9100 production process verification, part criticality, and documented changes to design or process.

AS9102 Form 2 documents product accountability for materials, special processes, and functional testing in a first article inspection. It links design and purchase order requirements to supporting records such as material certifications, process certifications, and test reports. It does not replace Form 3 dimensional verification or guarantee acceptance.

AS9100 auditors typically sample FAI evidence to confirm that first article requirements were planned, executed, reviewed, and controlled. They usually look for revision alignment, AS9102 records when required, ballooned characteristics, measurement results, material and process traceability, nonconformance handling, and re-FAI triggers.

Before an AS9102 FAIR is submitted, it usually needs at least quality approval, with engineering, manufacturing, configuration, supplier quality, or program approval added when the part, process, supplier evidence, drawing revision, nonconformance, or customer flowdown requires it.

Digital work instructions can reduce missing FAI data by linking inspection steps to ballooned characteristics, required fields, validation rules, and completion gates. They do not guarantee a complete or acceptable FAI unless source data, revisions, integrations, and change control are also managed.

During a partial FAI, resubmit the FAI records needed to prove the changed or affected characteristics, not the entire original package by default. At minimum, identify the reason for the partial FAI, reference the prior accepted FAI, and provide objective evidence for the affected requirements. Customer flowdowns may require more.

In most aerospace plants, Quality owns the FAI process, but day-to-day coordination is often handled by a quality engineer, FAI coordinator, or program quality role. Manufacturing engineering, planning, inspection, supply chain, and document control usually contribute evidence and approvals.