For an assembly FAI, Form 1 is the part number accountability form. Its job is to identify exactly what assembly the FAI covers, what design definition was used, and who is responsible for the report. In practice, the mandatory information is the set of required Form 1 fields defined by the current AS9102 form structure and any applicable customer flowdown.
For an assembly, Form 1 typically must include:
- FAI report number
- Part number of the assembly
- Part name
- Serial number, if applicable
- FAI type or reason, such as full or partial FAI where applicable
- Drawing number and drawing revision level, or other design definition identifier used to build and inspect the assembly
- Additional revision or change identifiers when required by the form or your configuration, such as a specification or process revision tied to product definition
- Organization name performing the FAI
- Supplier code or manufacturer identifier, if required by the form or customer
- Detail part numbers, subassembly part numbers, and associated FAIs listed in the accountability section for the assembly, where required
- Signature or approval fields, dates, and responsible person identification required to certify completion of the form within your controlled process
For assemblies, the accountability section matters. Form 1 is not just the top-level assembly header. It is also where you show the relationship to lower-level detail parts and subassemblies, including whether those items have their own completed FAIs. If a lower-level item is standard hardware or otherwise treated differently under your documented process and customer requirements, that treatment needs to be consistent with your FAI procedure and traceable.
What is not safe to assume is that every field is always populated the same way across every aerospace program. Some requirements depend on:
- The AS9102 revision your customer or contract invokes
- Whether the FAI is full, partial, or delta
- Whether the assembly includes make, buy, and outside-processed components
- How digital product definition is controlled in PLM or drawing management
- Customer-specific templates, portal rules, or Net-Inspect workflows
So the practical answer is: no, there is not a shorter assembly-only exception list that replaces Form 1 requirements. You still need the standard Form 1 accountability data, and for assemblies you must be especially careful that lower-level part accountability is complete, current, and linked to the correct revisions.
Common failure modes
- Top-level assembly part number matches, but one or more child part revisions do not
- Form 1 references a drawing revision that does not match the released build package
- Subassembly FAIs exist, but are not properly referenced in the assembly package
- Partial FAI is performed, but the form does not clearly identify the change trigger and affected scope
- ERP, MES, PLM, and FAI software use different part naming or revision conventions, creating reconciliation errors
In brownfield environments, these issues are common because Form 1 data is often pulled from multiple systems that were not designed around a single authoritative product definition. An FAI tool can help, but it does not remove the need for source-system alignment, controlled revisions, and validation of the data mapping. Full replacement of legacy systems is often unrealistic in regulated aerospace settings because of qualification burden, validation cost, downtime risk, and integration complexity. Most plants have to make Form 1 work across existing ERP, PLM, QMS, and inspection workflows.
If you need a definitive answer for a specific program, check three things together: the AS9102 revision in force, your customer flowdown, and your internal documented FAI procedure. That combination determines what is actually required in your environment.