Is AS9102 mandatory for all aerospace first articles?

AS9102 is not automatically mandatory for every aerospace first article. It becomes mandatory when it is explicitly required by one or more of the following:

• Customer contract or purchase order terms
• Customer quality clauses or supplier quality requirements
• Prime or Tier 1 flowdown requirements (e.g., via SQAR, Q-notes, S-specs)
• Your own QMS procedures that specify AS9102 as the standard FAI method

AS9102 is a widely adopted standard FAI format in aerospace, but it is still a standardized method, not a universal legal mandate. Some OEMs and defense programs require fully compliant AS9102 Forms 1, 2, and 3 for defined scope (e.g., all flight hardware, safety critical, or key characteristics). Others accept an equivalent FAI structured differently, as long as the information content meets their requirements.

In practice, this connects to digital AS9102 FAI when teams need to turn the answer into repeatable execution habits.

When AS9102 is typically required

• New part introduction on aerospace/defense programs that reference AS9100 and AS9102
• First build from a new supplier, site, or production line
• Configuration changes affecting fit, form, or function, when customer FAI re-trigger rules apply
• After major process changes (new machine, facility move, new manufacturing route) when required by contract or QMS

In these situations, the contract or OEM quality specification often calls out AS9102 explicitly, or references it as the default unless a different FAI format is agreed in writing.

When you might not use AS9102 format

There are common cases where a strict AS9102 form set is not used, even in aerospace:

• Internal FAIs for process validation where your QMS defines a different template but equivalent content
• Customer-specific FAI formats that differ from AS9102 (e.g., proprietary forms or portal-based workflows such as Net-Inspect configurations)
• Legacy programs started before AS9102 adoption, still running under older FAI conventions
• Non-flight or non-critical parts where the customer has not flowed down AS9102 or any formal FAI requirement

In these scenarios, what is mandatory is whatever your customer contract, applicable quality specs, and internal procedures say. You can be audited against your commitments, but not automatically against AS9102 if it is never invoked.

Brownfield reality and coexistence with other requirements

In most established aerospace plants, you will see multiple FAI regimes coexisting:

• Some programs requiring strict AS9102 compliance
• Some legacy or commercial programs using older or simplified FAI formats
• Some customer portals (e.g., Net-Inspect or OEM tools) that map to AS9102 concepts but use different data structures

This mix is typical in brownfield environments with long product lifecycles and many OEMs. Attempts to force a single, universal FAI format can run into resistance due to contractual constraints, qualification burden, and revalidation cost. Often the practical approach is to standardize data content and traceability while still producing the specific form or portal output each customer requires.

Key tradeoffs and constraints

• Compliance risk: If a contract or quality clause calls out AS9102, deviating from that format without written customer approval is a risk and can surface in audits.
• Internal consistency: If your QMS says “we perform AS9102 FAIs” in broad terms, auditors will expect evidence that FAIs follow the standard, not a patchwork of partial forms.
• Operational burden: Running AS9102 for every low-risk, non-critical part can add paperwork without commensurate value, especially in high-mix, low-volume environments.
• System limitations: Legacy MES, ERP, or PLM may not natively support AS9102 structures, so digital FAI often involves bolt-on tools or manual spreadsheets unless you invest in integration and validation.

Any change from non-AS9102 FAI to AS9102 (or vice versa) across programs should go through formal change control, including updates to procedures, training, and, where relevant, validated systems.

Practical guidance

To determine whether AS9102 is mandatory for a given first article:

1. Review the contract, PO, and referenced quality clauses for explicit AS9102 or FAI language.
2. Check the customer’s supplier quality manual / specifications for FAI expectations and re-trigger rules.
3. Confirm your internal QMS and work instructions: do they specify AS9102, an equivalent FAI, or program-specific rules?
4. Align with your customer quality representative before deviating from AS9102 on parts where expectations are unclear.

AS9102 is widely accepted because it standardizes expectations and evidence. But it is only mandatory where it has been made a requirement by contract, customer flowdown, or your own documented processes.