Defense contracts typically modify baseline AS9102 First Article Inspection requirements by adding contractual flowdowns on top of the standard. AS9102 defines a common FAI framework, but the binding requirement is usually the contract, purchase order, statement of work, customer quality clause, drawing note, or portal instruction. In practice, defense customers often require more evidence, tighter approval controls, specific submission formats, and additional data-handling restrictions.
This does not mean every defense program has the same FAI rules. Requirements vary by prime contractor, government customer, part criticality, program phase, export-control status, and whether the supplier is building to customer design, build-to-print, repair, or modified configuration.
Common contract additions to AS9102
Defense contracts commonly add requirements such as:
- Customer-specific FAIR submission rules: use of a required portal, template, naming convention, or electronic workflow such as a customer supplier portal or Net-Inspect-style process.
- Pre-shipment approval: requiring customer, prime, or government source inspection acceptance before product can ship. AS9102 alone does not always impose that business rule.
- Additional objective evidence: material certifications, special process certifications, test reports, inspection data, tool qualification evidence, calibration records, or operator qualification records.
- Key characteristic controls: added reporting or monitoring for critical, major, safety, fracture-critical, mission-critical, or customer-designated characteristics.
- Ballooning and characteristic accountability rules: specific expectations for drawing ballooning, characteristic numbering, embedded notes, model-based definition, specification callouts, and omitted characteristics.
- Delta or partial FAI triggers: stricter rules for when a change in design, process, supplier, tooling, CNC program, location, material source, or lapse in production requires a new or partial FAIR.
- Sub-tier supplier flowdown: requirements to collect, review, and retain FAI evidence from processors, machine shops, laboratories, or special process suppliers.
- Configuration and revision controls: explicit alignment to drawing revision, planning revision, work order, purchase order line, engineering change, and approved deviation or waiver status.
- Data security restrictions: ITAR, export-control, CUI, DFARS, or customer-specific handling rules for drawings, models, FAIR attachments, inspection data, and supplier access.
The contract is usually more specific than the standard
AS9102 is a baseline. A defense contract may require AS9102 compliance and then add program-specific conditions. Those additions can be more operationally important than the standard itself because they determine what the customer will accept, what evidence must be retained, and what must happen before shipment or invoicing.
The hard part is not usually understanding AS9102 in isolation. The hard part is reconciling AS9102 with the contract, quality clauses, engineering definition, customer portal rules, QMS procedures, and shop-floor execution records. If those sources do not agree, the organization needs a controlled interpretation and documented resolution path, not informal tribal judgment.
Where systems create risk
In brownfield aerospace and defense environments, FAI data often touches MES, ERP, PLM, QMS, document control, calibration, and supplier quality systems. Contract-specific FAI requirements can fail when these systems do not share revision, part, process, serial, lot, or supplier data consistently.
Common failure modes include submitting a FAIR against the wrong drawing revision, missing a flowed-down special process certificate, attaching export-controlled data to an uncontrolled system, approving a partial FAI without a clear change trigger, or shipping before required source inspection acceptance. These are process and data-governance failures, not just form-completion problems.
Full system replacement is usually unrealistic in established defense manufacturing environments. Qualification burden, validation cost, downtime risk, integration complexity, traceability obligations, and long equipment lifecycles usually force a more controlled approach: clear ownership, validated interfaces, governed templates, audit trails, and change-controlled mappings between systems.
What suppliers should verify
Before treating an AS9102 FAIR as complete for a defense contract, suppliers should verify the applicable contract clauses, customer quality requirements, drawing notes, source inspection requirements, export-control constraints, portal rules, and sub-tier evidence obligations. The FAIR may be technically complete under AS9102 but still unacceptable under the contract.
None of this guarantees customer acceptance, audit success, or regulatory compliance. It only reduces avoidable gaps when the contractual requirements are identified early, flowed into planning and inspection, and controlled through the same change-management discipline used for production configuration.