AS9102 Rev C Requirements: A Practical Guide for Aerospace Manufacturers

AS9102 Rev C tightens expectations on how aerospace manufacturers plan, execute, and document First Article Inspection (FAI). For quality and manufacturing teams already under pressure, the update raises an important question: what exactly changed, and how do we comply in a practical, digital way without slowing programs down?

This guide explains the AS9102 Rev C requirements, highlights key differences from Rev B, and shows how modern digital AS9102 software capabilities make day‑to‑day compliance manageable for OEMs and suppliers.

Overview of AS9102 Rev C and Its Purpose

AS9102 is the international aerospace standard that defines how organizations plan, perform, and document first article inspections. It sits alongside AS9100 and IAQG guidance as the primary reference for verifying that production processes can reliably manufacture conforming parts.

Why AS9102 Was Created and How It Supports AS9100 and Regulatory Expectations

AS9102 was created to solve a persistent industry problem: inconsistent and incomplete first article inspection practices across the aerospace supply chain. Before AS9102, each customer tended to define its own FAI rules and templates, creating confusion and rework for suppliers.

The standard provides:

• Common definitions for FAI scope, terminology, and documentation.
• Standardized forms (Forms 1, 2, and 3) to document part accountability, material and process verification, and characteristic results.
• Minimum expectations for traceability from design data (drawings, models, specifications) to inspection evidence.

AS9102 supports AS9100 by providing objective evidence that the production process has been validated. It also aligns with FAA, EASA, and other airworthiness regulators by demonstrating that initial and changed configurations are thoroughly verified before rate production.

Timeline of Revisions From Original Release to Rev C

AS9102 has evolved as follows:

• AS9102 (original release, 2004-era): Established the core concepts of FAI and the three standard forms.
• AS9102B (around 2009–2014 adoption window): Emphasized FAI planning and clarified expectations around documentation and re-accomplishment.
• AS9102C (Rev C, most recent): Focuses heavily on clarity for digital implementations, improved handling of partial and delta FAI, and better alignment with modern aerospace configuration and data-management practices.

For many organizations, Rev C has been the catalyst to move away from manual, spreadsheet-driven FAIRs and invest in digital solutions that can consistently interpret and enforce the updated requirements.

Who AS9102 Rev C Applies To in the Aerospace Supply Chain

AS9102 Rev C applies when it is invoked by contract, purchase order, or quality clause. Typically, it affects:

• OEMs and airframe manufacturers who must demonstrate configuration and process validation for new and changed parts.
• Tier 1 and Tier 2 suppliers who deliver flight-critical structures, engine components, avionics hardware, interiors, and other aerospace products requiring FAI.
• Special process providers whose outputs (heat treatment, NDT, plating, coatings) are essential to meeting drawing requirements documented on Form 2 and Form 3.

AS9102 itself is not a regulation; it is a standard. However, once a customer or prime specifies AS9102 Rev C, compliance becomes a contractual requirement and is often sampled during AS9100 and customer audits.

Core Requirements of AS9102 Rev C

AS9102 Rev C defines when an FAI is required, how to categorize it (full, partial, delta), and what information must be present on Forms 1, 2, and 3 to show complete characteristic accountability and traceability.

Full, Partial, and Delta FAI Definitions and Applicability

Under Rev C, FAI categories are more explicitly defined to match real-world change scenarios:

• Full FAI
  • Required for a new part number or when otherwise specified by the customer.
  • Covers all design characteristics and requirements shown on the applicable drawing or model, including notes, GD&T, and special requirements.
  • Generates a complete FAIR package (Forms 1–3 plus supporting evidence).
• Partial FAI
  • Used when only a subset of characteristics or operations need to be re-verified.
  • Often triggered by a change in manufacturing process, location, tooling, or equipment where design data is unchanged.
  • Documented clearly as a partial FAI on Form 1, with traceability to the baseline full FAI.
• Delta FAI
  • Used when an engineering or design change affects only certain characteristics.
  • Focuses on characteristics impacted by the design change, while referencing the baseline FAI for unchanged features.
  • Requires clear identification of revised design data and affected characteristics.

Rev C expects organizations to classify FAI correctly and to maintain traceable linkage between full, partial, and delta FAI so that the product’s verification history is transparent.

Mandatory Data Elements for Forms 1, 2, and 3

AS9102 Rev C retains the three-form structure but clarifies what must be captured on each form. While the standard’s exact field layout is copyrighted, you must ensure the following types of information are present and complete.

Form 1 – Part Number Accountability typically includes:

• Part number, name, and configuration (revision, issue, or version).
• FAI status (full, partial, delta) with cross-reference to the baseline FAIR when applicable.
• Serial number(s) or lot/batch identification for the first article units.
• Customer and internal references (PO, job/traveler, work order, etc.).
• Signatures, dates, and organization information for those who prepared and approved the FAIR.

Form 2 – Product Accountability focuses on:

• Materials used, including specification, type, and lot or heat numbers.
• Special processes such as heat treatment, NDT, welding, plating, coating, and surface treatments.
• Functional tests and performance verifications where results are pass/fail rather than dimensional.
• References to certifications, test reports, and process records (e.g., certificates of conformity, NADCAP approvals).

Form 3 – Characteristic Accountability, Verification Results, and Compatibility Evaluation documents:

• Each ballooned characteristic with a unique identifier/sequence number.
• Design requirement (nominal, tolerance, GD&T callout, or note description).
• Actual measured results or verification outcome.
• Acceptance status and compatibility evaluation where applicable.
• Links to the measurement method, inspection equipment, or CMM program as needed.

Rev C emphasizes that all applicable characteristics—including dimensions, notes, and special requirements—must appear on Form 3 so there is no ambiguity about what has been verified.

Requirements for Characteristic Accountability and Traceability

Characteristic accountability is the backbone of AS9102. Rev C expects you to demonstrate that every requirement in the design data has been identified, numbered, and verified with a clear record.

Practically, this means:

• Each drawing or model requirement is assigned a unique balloon number or similar identifier.
• That identifier is used as the sequence number on Form 3, creating one-to-one mapping between the drawing and FAIR.
• Measurement results, pass/fail decisions, and notes are recorded under the same identifier so anyone can trace from drawing to data and back.
• Special processes and materials that support a given characteristic are traceable via Form 2 and attached certifications.

Rev C strengthens the expectation that traceability must include configuration control. FAIRs must be tied to a specific drawing or model revision, and later delta/partial FAIs must clearly reference prior FAIRs and the changes that triggered them.

AS9102 Rev B vs Rev C: Key Changes

Organizations moving from Rev B to Rev C often underestimate the impact of the new revision. Much of the terminology is familiar, but Rev C clarifies intent, tightens definitions, and explicitly anticipates digital execution.

Clarifications Introduced for Digital Implementations

Rev C was written against the backdrop of widespread digital FAI tools rather than paper and spreadsheets. Some key clarifications include:

• Improved guidance on linking digital drawings/models to Forms 1–3, ensuring the configuration of the data source is clear.
• Recognition that digital signatures and electronic approvals can meet the standard as long as they are controlled and traceable.
• Expectations for consistent handling of multi-sheet drawings and multi-configuration parts in digital systems.
• Clearer distinction between the FAI process and the FAIR (report), which is important when using automated data flows.

These clarifications are not optional; they drive how digital solutions must behave to be considered aligned with Rev C.

Changes to Partial and Delta FAI Handling

Under Rev B, organizations frequently struggled with when and how to perform partial or delta FAI. Rev C addresses this by:

• More explicitly defining triggers for partial vs delta (manufacturing/process vs design/engineering driven).
• Reinforcing that partial and delta FAI must still maintain traceable linkage to the baseline full FAI.
• Emphasizing that only affected characteristics are re-verified, but documentation must clearly state what changed and why.

Done correctly, Rev C’s structure reduces unnecessary rework while still satisfying customer and regulatory expectations.

New or Reworded Fields and Expectations on the Forms

Rev C introduces reworded field descriptions and some additional expectations on how certain information is captured, for example:

• More precise language around FAI status (full, partial, delta) and its indication on Form 1.
• Clearer guidance on recording design data references (drawing/model numbers, revisions, specification references).
• More consistent terminology for compatibility evaluations and special characteristics.

Digital tools should be configured to reflect these Rev C expectations in field labels, required fields, and validation rules, even if the underlying data model is similar to what you used under Rev B.

Practical Triggers for AS9102 FAI Under Rev C

Knowing the theory is only half the story. Day-to-day, teams need a clear understanding of when Rev C expects a new FAI activity.

Design and Engineering Change Scenarios

Engineering changes that typically trigger full or delta FAI under Rev C include:

• New part introduction (new part number or first time build at your site).
• Changes that affect form, fit, function, reliability, or safety.
• Drawing or model revision that adds, deletes, or significantly changes key features.
• Tightening or relaxing tolerances on critical dimensions.
• New material specifications or design notes that drive new verification activities.

Most of these are handled via delta FAI, provided you can show clear traceability to prior FAIRs and focus only on affected characteristics.

Process, Material, and Supplier Changes

Process-oriented changes typically trigger partial FAI. Common examples include:

• Moving production to a new machine, cell, or facility.
• Changing the manufacturing route (e.g., switching from one machining sequence to another).
• Introducing new tooling or fixtures that could affect dimensions.
• Changing a sub-tier supplier for raw material, castings/forgings, or critical processes.
• Modifying process parameters for special processes (e.g., new heat treat cycle, new NDT technique).

Rev C expects organizations to have documented criteria—often in their QMS—for when such changes trigger partial FAI, and to demonstrate that the partial scope correctly corresponds to the impacted characteristics.

Lapse in Production and Customer-Specific Triggers

Another key trigger is lapse in production. If a part has not been produced for an extended period (commonly two years, but some customers specify different thresholds), Rev C expects you to reassess whether FAI is required. Many organizations treat this as a partial FAI unless design or process changes require more.

Customer-specific triggers may include:

• FAI required for every lot or every nth lot for high-risk parts.
• FAI required when internal yield or defect trends exceed thresholds.
• FAI mandated when a supplier changes certain sub-tiers, even if design and process remain stable.

AS9102 Rev C sets the baseline; purchase orders and customer quality clauses can add stricter conditions, and these must be interpreted alongside the standard.

How Digital AS9102 Software Supports Rev C Compliance

Trying to meet Rev C requirements with manual ballooning and spreadsheets is possible for simple parts, but it becomes risky and inefficient at aerospace scale. Modern AS9102 software is designed specifically to satisfy Rev C expectations while reducing cycle time and error rates.

Configuring Templates and Fields to Match the Rev C Standard

A robust digital solution lets you:

• Configure Form 1, 2, and 3 templates to align with Rev C’s required data elements and field definitions.
• Define mandatory fields and validation rules (e.g., FAI type required, drawing revision cannot be blank, serial numbers must match work orders).
• Standardize customer-specific layouts on top of a single, controlled data model.

This configuration step is critical to applying Rev C consistently across sites and suppliers.

Automated Checks to Prevent Common Nonconformances

AS9102 software can embed rule-based and automated checks such as:

• Verifying that every ballooned characteristic on the drawing has a corresponding entry on Form 3.
• Ensuring that FAI type (full/partial/delta) and baseline references are populated correctly on Form 1.
• Blocking approval if there are missing certificates for materials and processes referenced on Form 2.
• Highlighting inconsistencies between drawing revision, work order, and FAIR configuration.

These checks greatly reduce the risk of FAIR rejection by customers or findings during audits.

Managing Revisions, Partial, and Delta FAI in Software

Effective digital tools provide structured support for Rev C’s FAI types:

• Full FAI: Create a baseline FAIR that captures all characteristics and associated evidence.
• Partial FAI: Clone the baseline FAIR, restrict the scope to impacted operations/characteristics, and record the partial status on Form 1.
• Delta FAI: Compare new and prior design data to identify affected characteristics, generate a focused Form 3 subset, and clearly reference prior FAIRs.

Advanced systems can even visualize FAI lineage as a tree, showing which FAIRs are related to which design or process changes. This directly supports Rev C’s intent for transparent traceability.

Implementation Checklist for AS9102 Rev C

Moving to Rev C is not just a documentation update. It touches procedures, training, systems, and supplier expectations. The following checklist can guide implementation.

Gap Analysis From Current Practices to Rev C Requirements

Start by assessing your current state:

• Review quality procedures and work instructions against Rev C clauses.
• Audit sample FAIRs to check for complete characteristic accountability and clear FAI type identification.
• Evaluate whether partial/delta FAI usage matches Rev C definitions and triggers.
• Identify where manual workarounds (e.g., untracked spreadsheet columns) are substituting for systematic controls.

Document gaps and prioritize remediation based on risk, customer expectations, and audit feedback.

Training, Work Instructions, and System Updates

Next, update the human and procedural side:

• Revise FAI procedures to reference AS9102 Rev C explicitly, including FAI triggers and FAI type definitions.
• Update work instructions for quality engineers, inspectors, and manufacturing engineers, including clear guidance on how to classify and document FAI.
• Deliver role-specific training that focuses on practical scenarios rather than just standard text.
• Adjust your AS9102 software configuration (forms, validations, workflows) to reflect Rev C requirements and any customer-specific overlays.

The goal is that anyone involved in FAI can recognize when Rev C applies and how to execute it consistently in your chosen digital environment.

Ongoing Monitoring and Audit Readiness Under Rev C

Once Rev C is in place, you need continuous assurance that it is being followed:

• Periodically sample FAIRs for completeness, characteristic coverage, and alignment with design changes.
• Track FAIR rejection rates by customer and cause to identify systemic issues.
• Prepare for audits by ensuring FAIRs, supporting documents, and change histories are searchable and retrievable within minutes.
• Leverage digital dashboards, where available, to monitor open FAIRs, overdue approvals, and FAI bottlenecks.

Rev C does not require perfection, but it does expect a controlled, repeatable process with objective evidence to back it up.

Where AS9102 Rev C Fits in a Digital FAI Strategy

FAI should not be handled as a stand-alone, tactical task. Under Rev C, it is increasingly viewed as part of a broader digital aerospace operations strategy—one that connects design, planning, execution, and quality.

For a deeper look at how ballooning, Forms 1–3, workflows, and supplier collaboration come together in software, see the hub guide on AS9102 Software: Digital First Article Inspection for Aerospace Manufacturing.

By aligning your procedures, training, and AS9102 software with Rev C requirements, you reduce FAIR rejections, protect program schedules, and strengthen your position with OEMs and regulators—while turning FAI data into a reusable asset rather than a one-time deliverable.