AS9102 Form 1 Fields Explained: A Quality Engineer's Field Guide

A 48-hour window to submit a First Article Inspection Report. The customer's portal rejects it before an inspector even opens a calliper. Nine times out of ten, the rejection traces back to Form 1 — the Design Accountability / Part Number Accountability sheet. It looks like a header form, but every blank is a contractual declaration.

This guide walks through every field on AS9102 Rev C Form 1, explains what the standard actually requires, and flags the mistakes that earn corrective action requests before the part even reaches the CMM.

Why Form 1 Is More Than a Cover Sheet

AS9102 Rev C defines Form 1 as the Design Accountability record. Its job is to establish a clear, traceable link between the physical article being submitted and the design documentation that authorises it. Every downstream form — Form 2 (Product Accountability) and Form 3 (Characteristic Accountability) — inherits legitimacy from Form 1. If Form 1 is wrong, the entire FAIR is invalid.

The stakes are real. Aerospace primes specify contractual flow-downs that require a conforming FAIR before first shipment. A rejected Form 1 can push a production release date by weeks. Understanding each field is risk management, not administrative housekeeping.

For a broader view of all three forms and how they relate, see AS9102 Forms 1, 2 & 3 Explained. If your programme uses a delta FAI after a design change, the rules in Delta FAI Explained also affect what you declare on Form 1.

Form 1 Fields — Line by Line

The table below covers the standard fields on AS9102 Rev C Form 1, organised as they typically appear in the published appendix. Field labels follow the standard's own terminology; always refer to the published SAE AS9102 Rev C document for the definitive field sequence, as layout details can vary by edition printing.

Part Number Accountability: What the Standard Really Means

AS9102 Rev C establishes design accountability as a core requirement of Form 1. The obligation is not simply to state the part number — it is to demonstrate that every design document controlling the article has been identified and is at the correct revision. This includes the top-level drawing, any dash-number detail drawings, referenced specifications, and any customer-supplied design authority documents.

A multi-detail drawing — one sheet covering several part numbers — is a common source of error. Each dash number is a separate part and requires its own Form 1. Submitting one Form 1 for a drawing that covers four dash numbers is a non-conformance, even if all four appear on the same physical sheet.

Sub-tier supplier parts also fall under part number accountability. If the article is an assembly, Form 2 carries the sub-tier content — but Form 1 must acknowledge that sub-tier design data exists and is controlled. Forgetting to reference a sub-tier drawing number in the additional specifications field is a recurring audit finding.

The FAIR Identifier — Small Field, Big Consequences

The FAIR Identifier is the single key that links Form 1 to Form 2, Form 3, material certificates, process certifications, and customer submission records. If any of those documents carry a different number, traceability breaks. Some quality engineers treat this as a free-text field and assign numbers ad hoc — until an auditor asks for FAI-2022-0047 and the file server has it labelled FAI_Bracket_Rev3_Final_v2.

Best practice is a three-segment identifier: an organisation prefix (three to five characters), a four-digit year, and a zero-padded sequential number — for example, CNX-2024-00117. Define the format in your FAI procedure and enforce it in your QMS. Some customers, particularly Tier 1 primes, assign their own FAIR identifier and require you to use it alongside your internal number; check contract requirements before issuing the first FAI package.

FAI Reason Codes — Triggers Defined by AS9102 Rev C

AS9102 Rev C defines the circumstances that require a new or updated FAI. These include: a new part number being released to production; a change in design, manufacturing process, or applicable specification that may affect form, fit, or function; a change in manufacturing source or location; a change to numerical control programmes or tooling that may affect a characteristic; and a lapse in production exceeding two years. Customers frequently add further triggers through quality flow-down clauses in the purchase order.

When completing the reason code field, state the applicable trigger and a brief description — do not leave it as a single word. If you are unsure whether a specific process change qualifies as a trigger, consult the published SAE AS9102 Rev C standard and your customer's quality representative before proceeding. Shipping product without a required FAI carries far greater risk than requesting clarification. The AS9102 Rev B vs Rev C post covers how trigger definitions evolved between revisions.

Form 1 Instructions — Step-by-Step Fill Sequence

1. Retrieve the controlling drawing. Always work from the revision stated on the purchase order. If the drawing in your system differs from the PO revision, resolve the discrepancy with the customer before continuing.
2. Populate part number, part name, revision, drawing number, and drawing revision directly from the drawing title block. Character-by-character accuracy matters. A trailing space or a misplaced dash will fail an automated string-match in customer portals such as Net-Inspect or OASIS.
3. List all referenced specifications in the additional planning field. Read every note and requirement block on the drawing. Aerospace drawings routinely reference AMS, BAC, ASTM, and NADCAP process specifications. Each must be listed with its applicable revision.
4. Assign the FAIR Identifier first, before any other forms or inspection records are created. Stamp this number on every related document immediately so traceability is established from the outset.
5. Select the correct reason code. If you are unsure whether a process change triggers a new FAI, consult the standard's trigger definitions and the customer's quality flow-down. An unrequested FAI is better than a shipment hold.
6. Enter the manufacturing location with the full street address. Aerospace supply chain management systems cross-reference this against approved manufacturer lists (AML). A city name alone will not pass.
7. Record the serial or lot number of the actual article inspected. Pull it from the physical part tag or traveller, not from a planned number. The article on the inspection table is the article on the FAIR.
8. Date and sign only after all three forms are complete and reviewed. Pre-signing Form 1 and then making corrections to Form 3 creates a documentation integrity issue. The completion date on Form 1 should be the latest date across all three forms.

Common Mistakes on Form 1 and How to Avoid Them

• Copying from a previous FAIR. If revision level or PO number changed, you now have a Form 1 with stale data. Always build from the current drawing, not a saved template with prefilled values.
• Listing only the prime specification, not sub-tier specs. The additional planning field must capture every spec on the drawing face. Missing AMS2750 (pyrometry) or NADCAP-required process specs will fail a customer audit even if the parts are dimensionally perfect.
• Using the internal sales order instead of the customer PO. Customers match the PO number field to their procurement system. Your internal order number is invisible to them.
• Confusing drawing revision with part revision. On older aerospace drawings these are often the same letter, but on designs under model-based definition or PDM control they can diverge. The part revision and drawing revision fields are separate for a reason — treat them independently.
• Leaving the full/partial indicator blank on a delta FAI. If a partial FAI was conducted after a process change, it must be declared partial and the customer approval referenced. Submitting it as a full FAI when not all characteristics were re-inspected is a falsification of records — a serious QMS non-conformance.
• Non-matching FAIR Identifiers across forms. Spot-check that the identifier in the FAIR number field appears identically on the header of every Form 2 and Form 3 page before submission.

Frequently Asked Questions

What is the difference between the Part Number field and the Drawing Number field on AS9102 Form 1?

The part number field identifies the specific article — it may include a dash number for a detail within a multi-detail drawing. The drawing number field identifies the controlling document. On simple single-detail drawings they are identical, but on assembly or multi-detail drawings one drawing can cover several part numbers. Both fields must be completed independently because they serve different traceability functions.

What should I put in the FAIR Identifier field if my customer assigns their own FAI number?

Enter your internal FAIR Identifier in the FAI number field and note the customer-assigned reference in the remarks or additional planning section, depending on the customer's specific instructions. Some customer portals require their own reference number as the primary identifier — check the quality flow-down clauses in your purchase order before submitting.

Can I submit a single Form 1 for an assembly that includes several sub-components?

No. Each part number requires its own Form 1. The top-level assembly has one Form 1, and each purchased or manufactured sub-component with its own part number requires a separate FAIR, which may be submitted as a sub-tier package. AS9102 Rev C is explicit that design accountability is established at the part number level, not the assembly level.

How long must completed Form 1 records be retained?

AS9102 Rev C does not specify a retention period directly; it defers to the contract and the organisation's QMS. Most aerospace primes require retention for the life of the part plus a defined period — commonly 10 years or the duration stated in the contract, whichever is longer. Review the documented information retention requirements in AS9100 Rev D and your customer's quality flow-down for the exact requirement applicable to your programme.

What triggers require a new FAI under AS9102 Rev C?

AS9102 Rev C defines triggers including: a new part number released to production; a change in design, process, or specification that may affect form, fit, or function; a change in manufacturing source or location; a change to NC programmes or tooling affecting a characteristic; and a production lapse exceeding two years. Customers may define additional triggers in their purchase order quality clauses. Always verify against the contractual flow-down, not only the base standard. See also First Article Inspection Checklist for a pre-submission gate review.

Conclusion

Form 1 is the foundation of every AS9102 FAIR package. Errors here propagate across all three forms and can invalidate weeks of inspection work. The key discipline is straightforward: populate every field from the source document, assign the FAIR Identifier before any other work begins, and sign only after all three forms are reviewed. Quality engineers who treat Form 1 as a quick header are the ones waiting for corrective action responses.

For a deeper look at how the three forms connect and what each downstream form requires, see AS9102 Forms 1, 2 & 3 Explained.