How to Complete AS9102 Form 1 Part Number Traceability

Quick answer: Completing AS9102 Form 1 part number traceability means recording the exact drawing part number, revision level, design documentation source, and physical part identifier on the Form 1 header so that an auditor can trace the inspected article back to an authorized design record without ambiguity. Every field must match the released drawing — character for character.

Why Form 1 Part-Number Errors Are the Leading Cause of FAI Rejections

Part-number and revision mismatches on Form 1 are the single most frequent reason aerospace customers reject an FAI package on first submission. The root cause is structural: Form 1 is completed by a quality engineer working from documents, while the physical part was produced by manufacturing working from a potentially different revision of those same documents. Any gap between those two revision states — even a single suffix letter — makes the FAI non-conforming under AS9102 Rev C Section 4.

Unlike a dimensional non-conformance, which can sometimes be disposition-approved by engineering, a Form 1 traceability error cannot be waived away. The entire FAI must be re-submitted with corrected documentation, restarting the customer review clock. In aerospace programmes where customer approval cycles run four to six weeks, a single Form 1 error can push a delivery slot by a full quarter. Understanding exactly how to populate Form 1 — particularly the part number, revision, and design documentation fields — is therefore one of the highest-return skills a quality engineer in this industry can develop.

What Is Actually at Stake

AS9102 Rev C (the current edition, published by SAE International) governs first article inspection requirements for aviation, space, and defence manufacturers. Form 1 is the Design Documentation header that establishes the who, what, and which-version of the part being inspected. Customers — primes like Airbus, Boeing, Safran, or GE Aviation — use Form 1 to verify that the part presented for FAI was produced to the correct, current design authority.

A mismatch between Form 1 data and the released drawing triggers a mandatory re-inspection under AS9102 Rev C Section 4. That means new balloons, new measurements, new sign-offs, and a revised submittal. For a complex machined housing, that can represent 40 to 80 hours of rework.

The three most frequently audited traceability fields are: (1) the full part number with dash suffix, (2) the drawing revision level, and (3) the design documentation type and source identifier. Getting all three right simultaneously, on the first attempt, is the goal of this guide.

How to Complete AS9102 Form 1 Part Number Traceability: Step by Step

Work through these steps in order. Each step maps to a specific field or block on the AS9102 Rev C Form 1 template. If your customer supplies their own Form 1 variant, the field names may differ slightly, but the underlying data requirement is the same.

1. Retrieve the authorized design record before touching Form 1.
   Pull the drawing or model-based definition from your document control system — not from email, not from a shared drive folder, and not from memory. Confirm the document is at the latest approved revision by checking its release stamp or ECN sign-off. If your customer controls the drawing, confirm you hold the same revision they are referencing. This single step prevents the majority of Form 1 rejections.
2. Transcribe the part number exactly as it appears on the design record.
   Copy every character: base number, dash number, alpha suffix, and index. Common traps include leading zeros that get dropped (04471 becoming 4471), lowercase letters that appear uppercase on older drawings, and space-vs-hyphen differences. Do not interpret or abbreviate. If the drawing says AXL-0047-1-REV-C, write exactly that.
3. Record the revision level in its own dedicated field.
   AS9102 Rev C Form 1 has a separate Revision field. Do not embed the revision inside the part number field. If the drawing uses numeric revisions (Rev 3), record the numeral. If it uses alpha (Rev D), record the letter. If the drawing uses a dash-number system where each dash number carries its own revision — common in defence programmes — record the revision for the specific dash number being inspected, not the highest revision across all dash numbers.
4. Identify the design documentation type and source.
   AS9102 Rev C Section 8.1 lists accepted design documentation types. Fill the corresponding Form 1 field as one of the following, matching your actual source:
   • 2D Drawing — a released dimensioned drawing in PDF, TIFF, or paper format.
   • Model-Based Definition (MBD) — a 3D annotated model per ASME Y14.41-2019 or equivalent. Record the model file name, revision, and authoring standard.
   • Digital Product Definition (DPD) — common in Boeing supply chains; record the DPD number and issue.
   • Specification or Standard — when a catalogue part is inspected against a published standard (e.g., NAS, MS, AN) rather than a proprietary drawing.
   Never write "Customer Drawing" as the documentation type — it is not a recognized category in AS9102 Rev C and signals to the reviewer that the preparer is unfamiliar with the standard.
5. Enter the part serial number or lot identifier.
   AS9102 Rev C requires physical traceability from Form 1 back to the specific article inspected. If the part is serialized, enter the serial number. If it is lot-controlled, enter the lot number and quantity inspected. That identifier must also appear on the physical part — on a tag, traveller, or laser-etched mark — before inspection begins. Record the identification method (e.g., "electro-etch on non-functional surface") in the remarks field if your customer requires it.
6. Confirm the organization name, CAGE code, and FAI date.
   The organization name must match your AS9100 quality management system certificate exactly. The CAGE code must be the code assigned to the facility performing the FAI, not the parent company's code if you operate from a separate site. The FAI date is the date the first article part was completed and released for inspection — not the date the report was typed up.
7. Record the drawing index or sheet reference if multi-sheet.
   For drawings with multiple sheets, Form 1 should reference all sheets included in the design record. If a sheet was superseded by an ECN but your customer has not yet released the updated drawing package, note the discrepancy in the remarks block and attach the ECN as supporting evidence. Do not silently use a higher-revision sheet without documenting it.
8. Cross-reference Form 1 to Forms 2 and 3 before final sign-off.
   Every characteristic on Forms 2 and 3 must trace back to the same drawing revision recorded on Form 1. If a characteristic was ballooned from a later revision — even informally — the entire FAI is invalid. Do a final check: balloon number 1 on Form 2 must appear on the same drawing revision entered in Form 1, Sheet 1. CadNexa's FAI Report Generator carries the Form 1 header identifiers consistently across Forms 2 and 3, eliminating this class of transcription error.
9. Obtain authorized signatures.
   AS9102 Rev C requires Form 1 to be signed by the FAI responsible party — typically the quality representative at the manufacturing site. Some customers also require a design authority counter-signature. Check your customer's Purchase Order or Quality Clauses for specific signatory requirements. Electronic signatures are acceptable if your QMS and the customer's purchase order permit them.

AS9102 Form 1 Key Fields: Quick Reference

Design Documentation Requirements: What AS9102 Rev C Actually Says

Section 8.1 of AS9102 Rev C states that the FAI shall verify conformance to the design documentation. "Design documentation" encompasses the drawing, applicable specifications (material, process, finish), and any notes or general tolerances that form part of the design record. For aerospace parts, that typically includes:

• The primary detail drawing or MBD dataset
• Referenced material specifications (e.g., AMS 2770 for aluminium heat treatment, AMS 4928 for titanium bar)
• Surface finish standards (e.g., Ra values per ASME B46.1)
• General tolerance notes (e.g., ISO 2768-m for linear tolerances where no tolerance is explicitly stated)
• Applicable process specifications called out in drawing notes

Form 1 is where the preparer declares which version of each document was used. If a material specification was revised between when the quote was won and when the FAI was performed, the newer specification governs — and Form 1 must reflect it. Traceability is a live chain, not a snapshot taken at contract award. For a deeper look at how Forms 1, 2, and 3 interconnect, see the AS9102 Forms 1, 2 and 3 Explained guide on this site.

If your customer is IAQG-registered, supporting guidance is also available through the IAQG OASIS database.

Revision Control: The Traceability Requirement Most Teams Get Wrong

Revision control on Form 1 is not just about writing down a letter or number. It is about documenting the revision of every design document that governed production of that specific article. Consider a part produced to Drawing Rev D, but the material specification referenced on the drawing was updated from AMS 4928 Rev G to Rev H three weeks before FAI. If the raw material was procured under Rev G and Form 1 records Rev H, there is a traceability gap that an auditor will find.

Best practice is to lock the complete design record package — drawing, all referenced specs, and all applicable notes — at the time the FAI part enters production. Record each document and its revision on Form 1 or in an attached document list referenced from Form 1's remarks field. This gives the customer a complete revision snapshot and protects your organization during subsequent audits.

For teams managing multiple active part numbers across several customer programmes, a spreadsheet revision tracker quickly becomes unmanageable. A controlled document register within your QMS is the minimum acceptable approach for maintaining this discipline consistently.

See also the AS9102 Rev B vs Rev C breakdown for a summary of how revision control requirements changed between editions — particularly relevant if your customers still reference the older Rev B language in legacy purchase orders.

Common Mistakes and How to Avoid Them

• Copying Form 1 from a previous FAI. Teams reuse old Form 1 templates to save time and forget to update the revision field. Always regenerate Form 1 from the current design record for each new FAI submission.
• Not validating the customer's current revision before starting inspection. Customers issue drawing revisions independently of your internal document control cycle. Confirm the customer's current revision directly with their programme quality contact before ballooning a single dimension.
• Entering the drawing number in the part number field. These are sometimes — but not always — the same. Many aerospace programmes use a separate drawing number and part number. Check the title block carefully; both may be required on Form 1 in separate fields.
• Omitting sub-tier FAI traceability. If your part incorporates a purchased detail part that is also subject to FAI, the sub-tier supplier's Form 1 must be in your package and referenced from your Form 1. Missing this is a common AS9100 audit finding.
• Signing Form 1 before inspection is complete. The FAI date and signature signify that the full FAI was performed. Signing early — to meet a deadline — and then adding characteristics later is a records integrity issue that can escalate to a quality escape.
• Ignoring customer-specific quality clauses. Primes like Boeing (D6-51991), Airbus (AIPI 00-00-002), and Safran apply supplementary FAI requirements on top of AS9102 Rev C. These clauses sometimes require additional fields on Form 1 or impose stricter traceability evidence. Read every applicable quality clause before completing Form 1.

How CadNexa Helps

Once Form 1 is populated correctly, the next task is completing Forms 2 and 3 — which means ballooning the drawing and recording every characteristic. CadNexa's FAI Report Generator (live at cadnexa.com/app.html) generates AS9102 Rev C-compliant reports including Form 1 directly from your balloon data. The part number, revision, design documentation type, CAGE code, and FAI date entered in the Form 1 header are carried consistently across Forms 2 and 3, eliminating the transcription errors that cause revision mismatches. Export as interactive HTML, PDF, or CSV for customer submission.

The Box+Balloon OCR feature reads dimension values, tolerances, and GD&T frames directly from your PDF drawing, so the same session that captures your characteristics also seeds the Form 2 characteristic list. For high-characteristic-count aerospace parts — where a structural bracket might carry 120-plus ballooned dimensions — this is where manual transcription risk is highest and where automation delivers the clearest return. The tool can be explored without signing up using the bundled sample drawings in guest mode.

Frequently Asked Questions

What part number information is required on AS9102 Form 1?

Form 1 requires the full drawing part number including revision level, part name, drawing number, design documentation source (such as model-based or 2D drawing), FAI part serial or lot number, and the organization's name and CAGE code. Every field must match the design record exactly with no abbreviations or omissions.

Does AS9102 Rev C require a serial number for every FAI part?

AS9102 Rev C requires the part to be identified by a serial number or, where serialization is not required by the design record, a lot or batch identifier. The chosen identifier must appear on Form 1 and physically on the part or its traveller tag to maintain traceability throughout the FAI.

What revision level must be recorded on AS9102 Form 1?

The revision level shown on Form 1 must exactly match the authorized design record used to produce the FAI part — including any dash numbers, index letters, or amendment suffixes. Recording an obsolete or unapproved revision is one of the most common causes of FAI rejection by aerospace customers.

Is a model-based definition acceptable as the design documentation source on Form 1?

Yes. AS9102 Rev C recognizes model-based definition (MBD) as a valid design documentation source. When MBD is used, Form 1 must record the 3D model file name, revision, and the software standard used to create it (such as ASME Y14.41-2019). A 2D PDF extracted from the model is not a substitute for the authoritative MBD dataset.

Can one Form 1 cover multiple part numbers in an assembly FAI?

No. AS9102 Rev C requires a separate Form 1 for each unique part number included in the first article inspection. For a sub-assembly FAI, each purchased or manufactured detail part that is subject to FAI requirements gets its own Form 1, with the top-level assembly Form 1 referencing the lower-level FAI records.

Conclusion

Form 1 part number traceability is the foundation on which every other AS9102 document rests. Get the part number, revision level, and design documentation type right — exactly right — and the rest of the FAI package has a solid anchor. Get any one of those wrong and the entire submission is suspect, regardless of how accurate the measurement data looks.

The steps above — retrieving the authorized design record first, transcribing every character exactly, recording the revision in its own field, identifying the documentation type correctly, and linking physical part traceability to Form 1 — are not complex. They are disciplined. Build them into a pre-inspection checklist, and Form 1 rejection notices will stop arriving. For the end-to-end FAI workflow that surrounds Form 1, the First Article Inspection Checklist on this site is a practical next read.