Winning an aerospace or defence contract is only the beginning. Before a single production part ships, your customer expects proof that your process produces exactly what the drawing specifies, that every controlled characteristic has been verified, and that the records behind those claims will survive an audit years later. This is where two frameworks meet: AS9100, the aerospace quality management system standard, and AS9102, the standard that governs First Article Inspection. Manufacturers who treat these as paperwork exercises tend to scramble before audits and lose points on findings. Manufacturers who embed the requirements into a purpose-built ERP tend to stay audit-ready continuously. This guide explains what each standard actually requires, where manufacturers most often fail, and how an aerospace ERP enforces compliance day after day rather than the week before the auditor arrives.
To see how these requirements are handled in software, explore our AS9100 ERP software and dedicated First Article Inspection (AS9102) software.
What AS9100 Actually Requires
AS9100 is the aerospace quality management system standard maintained under the International Aerospace Quality Group. It is built on the full text of ISO 9001, then adds requirements specific to the risks of aviation, space, and defence. If you already understand ISO 9001, think of AS9100 as that foundation plus a set of sector-critical controls that reflect how costly a defect can be when a part flies.
The aerospace-specific additions matter because they define what an auditor will probe beyond generic quality management. The most consequential include the following.
- Risk management. Operational risk must be identified, assessed, and controlled across the product lifecycle, not just discussed at a management review.
- Configuration management. You must know precisely which revision of which drawing, specification, and process applies to each part and each order, and you must control changes to that configuration.
- Counterfeit part prevention. Processes must reduce the risk of counterfeit or fraudulent parts entering the supply chain, a serious concern for electronic components and raw material.
- Product safety. The organisation must plan and manage the activities that assure product safety throughout realisation.
- Special process control. Processes whose results cannot be fully verified by later inspection, such as heat treatment, welding, and surface finishing, must be validated and controlled, often under Nadcap accreditation.
Certification to AS9100 is not a one-time event. It is a system that must demonstrate control every day, produce objective evidence on demand, and improve through corrective action. That continuous-evidence expectation is exactly why spreadsheets and shared folders struggle, and why a system of record built for aerospace pays for itself.
What AS9102 First Article Inspection Is
First Article Inspection, governed by AS9102, is the documented verification that a production process produces a part that conforms to every requirement of the drawing and the purchase order. It is performed on a representative part made using the same tooling, methods, and process that production will use. The output is the First Article Inspection Report, or FAIR, which becomes objective evidence that the process was proven before volume production began.
AS9102 organises the FAIR around three forms, each answering a different question.
- Form 1, Part Number Accountability. Identifies the part, drawing, revision, purchase order, and the assemblies or sub-components involved, and records whether the FAI is complete or partial.
- Form 2, Product Accountability. Records the materials, special processes, and functional testing used, along with the certifications that support them, such as material certs and process approvals.
- Form 3, Characteristic Accountability. Lists every design characteristic, its specified value and tolerance, the actual measured result, and the inspection method used to verify it.
Characteristic Accountability and Ballooning
The heart of a FAIR is the principle that every characteristic on the drawing must be accounted for. To achieve this, each requirement on the engineering drawing is uniquely numbered, a practice known as ballooning, so that a balloon on the drawing maps one-to-one to a line on Form 3. Nothing is allowed to fall through the gaps: a dimension, a note, a surface finish callout, or a material specification each becomes a numbered characteristic with a documented result. When an auditor cross-references a balloon number on the drawing against the matching row on Form 3 and finds the measured value and inspection method, that is characteristic accountability working as intended.
When a Re-FAI Is Triggered
A First Article Inspection is not permanent. AS9102 requires a full or partial re-accomplishment of the FAI when specific changes occur, because those changes can affect conformance. Common triggers include a change to the design or drawing revision, a change in manufacturing source, process, or location, a change in tooling or numerical control program that can affect the part, a lapse in production long enough to raise doubt about process control, and a corrective action that changes the manufacturing process. A partial re-FAI addresses only the characteristics affected by the change, but the accountability rules still apply. Missing a re-FAI trigger is one of the quieter ways a compliant-looking part becomes a nonconformance waiting to be discovered.
Why Manufacturers Fail Audits
Audit findings rarely come from a company that cannot make good parts. They come from a company that cannot prove it. The failure modes are predictable and, importantly, avoidable with the right controls.
| Failure mode | What it looks like | Underlying cause |
|---|---|---|
| Missing records | A material cert or inspection result cannot be located during the audit | Records live in email, folders, and paper with no single system of record |
| Wrong revision | Parts were built or inspected against a superseded drawing revision | Weak configuration control and no link between order, drawing, and revision |
| Incomplete FAIR | Characteristics on the drawing have no matching Form 3 line or no measured result | Manual ballooning and transcription with no enforced completeness check |
| Broken traceability | A serialised part cannot be tied back to its lot, material, and process records | Traceability captured inconsistently across disconnected tools |
| Open nonconformances | NCRs and corrective actions left unresolved past due dates | No closed-loop workflow linking findings to root cause and verification |
| Missed re-FAI | A drawing or process change shipped without re-accomplishing the FAI | Change events are not connected to quality gates that force a re-FAI |
Notice the pattern. Every failure mode traces back to disconnected information and manual handoffs. When quality data, engineering revisions, purchasing certs, and production records live in separate places, the burden of proving compliance falls on people remembering to reconcile them. That is exactly the burden an ERP is built to remove.
How ERP Enforces Compliance Continuously
An aerospace ERP does not replace your quality team or your inspectors. It removes the manual reconciliation that lets defects and gaps hide, and it turns compliance from an event into a state. Below are the specific mechanisms that matter, and how each maps to an AS9100 or AS9102 requirement.
Quality Gates That Stop the Line
A quality gate is a mandatory checkpoint the ERP enforces before work advances. A part cannot move from inspection to shipping if a required inspection result is missing, if the FAIR is incomplete, or if an open nonconformance is attached. Because the gate is enforced by the system rather than a checklist someone may skip, the process cannot silently bypass a control. This is how AS9100 clauses on control of production and release of products become continuous rather than aspirational.
Ballooning and Digital FAIR
Instead of hand-numbering a drawing and retyping values into a spreadsheet, an ERP with digital First Article Inspection lets you balloon the drawing once and generate the Form 1, Form 2, and Form 3 structure automatically. Every balloon becomes a characteristic line that must be resolved with a measured result and an inspection method before the FAIR can be marked complete. The system enforces characteristic accountability by refusing to close a FAIR that has unresolved characteristics, which directly addresses the incomplete-FAIR failure mode. When a drawing revision changes, the system can flag the affected characteristics and drive a partial re-FAI rather than relying on memory.
NCR and CAPA as a Closed Loop
When an inspection fails, the ERP raises a Nonconformance Report and links it to the exact part, lot, order, and characteristic involved. From there a Corrective and Preventive Action workflow drives root-cause analysis, containment, corrective action, and verification of effectiveness, with due dates and ownership tracked. Because the NCR is linked to a quality gate, an open nonconformance can block release until it is resolved. This closed loop is what auditors look for when they test whether your corrective action process actually prevents recurrence.
Serial and Lot Traceability
Aerospace traceability means being able to answer, for any serialised or lot-controlled part, which raw material heat, which operator, which machine, which process certification, and which inspection records produced it, and conversely, if a material lot is suspect, which finished parts it touched. An ERP captures this genealogy automatically as work moves through operations, so traceability is a byproduct of doing the work rather than a separate documentation task. This is the backbone of both configuration management and counterfeit-part investigations.
Certificates of Conformance and Document Control
A Certificate of Conformance is the supplier statement that the delivered product meets its requirements. An ERP can generate a Certificate of Conformance automatically from the actual quality records tied to the shipment, pulling in the correct part number, revision, purchase order, and supporting certifications rather than relying on a manually maintained template. Coupled with controlled document management, this ensures the certificate reflects the real, current configuration and that superseded revisions are not in circulation.
Configuration and Revision Control
Because the ERP links each order to a specific part, drawing, and revision, it prevents the wrong-revision failure mode at its source. When engineering releases a new revision, the system controls where and when the change takes effect, which open orders are affected, and whether a re-FAI is required. Configuration management stops being a document someone maintains and becomes a live property of every transaction.
Audit-Ready Dashboards
Finally, an ERP gives quality leaders a live view of compliance status: open nonconformances by age, FAIRs pending completion, certifications approaching expiry, special processes and their Nadcap status, and overdue corrective actions. Instead of assembling evidence in a panic before an audit, the team maintains a green dashboard continuously and can produce any record on demand. The audit becomes a confirmation of a state you already maintain rather than a test you cram for.
Mapping Requirements to ERP Controls
| Standard requirement | ERP control that enforces it |
|---|---|
| AS9100 control of production and release | System-enforced quality gates that block advancement |
| AS9100 configuration management | Order-to-drawing-to-revision linkage with change control |
| AS9100 nonconformity and corrective action | Linked NCR and CAPA closed-loop workflow |
| AS9100 counterfeit part prevention | Serial and lot traceability with material genealogy |
| AS9102 characteristic accountability | Digital ballooning and completeness-enforced Form 3 |
| AS9102 re-FAI on change | Change events that trigger partial or full re-FAI |
| Product conformance evidence | Auto-generated Certificates of Conformance from records |
Putting It Together on the Shop Floor
Consider a machined structural fitting entering production. Engineering releases the drawing at a controlled revision, and the ERP ties that revision to the customer order. An inspector balloons the drawing inside the system, and the ERP builds the Form 3 characteristic list automatically. As the first article is measured, results populate against each balloon, and the FAIR cannot close until every characteristic has a result and method. Material certs and special-process approvals attach to Form 2, and serial traceability records the heat lot and machine. A quality gate prevents shipment until the FAIR is complete and no nonconformance is open. When the shipment goes out, the ERP generates the Certificate of Conformance from those exact records. Months later, when a change to the numerical control program is proposed, the system flags a partial re-FAI for the affected characteristics before any changed part can ship. At no point did anyone have to remember to reconcile a spreadsheet, and at every point the evidence was captured as a byproduct of the work.
That is the difference between chasing compliance and enforcing it. The standards define what good looks like; the ERP makes good the path of least resistance. For aerospace and defence manufacturers, that shift is what turns audits from a recurring fire drill into a routine confirmation of how they already operate.
Key Takeaways
- AS9100 is the aerospace quality management standard built on ISO 9001 plus sector controls for risk, configuration management, counterfeit-part prevention, product safety, and special processes.
- AS9102 First Article Inspection proves a production process conforms, using Forms 1, 2, and 3, with characteristic accountability enforced through ballooning.
- A re-FAI is triggered by design or revision changes, process or source changes, tooling changes, production lapses, and process-altering corrective actions.
- Most audit failures come from missing records, wrong revisions, incomplete FAIRs, broken traceability, and open nonconformances, all rooted in disconnected tools.
- An ERP enforces compliance continuously through quality gates, digital ballooning and FAIR, closed-loop NCR and CAPA, serial traceability, auto-generated Certificates of Conformance, and audit-ready dashboards.
Frequently Asked Questions
AS9100 requires organisations to verify that products meet requirements, and First Article Inspection is the recognised aerospace method for proving a production process conforms before volume manufacturing. Most aerospace customers contractually require AS9102 FAI, so in practice it is treated as mandatory even though it is a separate standard from AS9100 itself.
Form 1 covers Part Number Accountability, identifying the part, drawing, revision, and order. Form 2 covers Product Accountability, recording materials, special processes, and functional testing with supporting certifications. Form 3 covers Characteristic Accountability, listing every design characteristic with its specified value, measured result, and inspection method.
Characteristic accountability is the requirement that every design characteristic on the drawing is uniquely identified and verified. Each requirement is ballooned with a unique number, and each balloon maps to a line on Form 3 with a measured result. Nothing on the drawing is allowed to go unverified, which is why completeness is the core test of a valid FAIR.
Common triggers include a change to the design or drawing revision, a change in manufacturing source, process, or location, a change in tooling or numerical control program that affects the part, a significant lapse in production, and a corrective action that alters the manufacturing process. A partial re-FAI addresses only the affected characteristics, while other changes may require a full re-FAI.
AS9100 contains the entire ISO 9001 quality management standard and adds aerospace-specific requirements on top. Those additions include risk management, configuration management, counterfeit part prevention, product safety, and control of special processes. In short, every AS9100 requirement includes ISO 9001, plus controls that reflect the higher stakes of aviation, space, and defence.
An ERP enforces quality gates, keeps a single system of record for inspection results and certifications, links each order to the correct drawing revision, drives NCR and CAPA to closure, captures serial traceability automatically, and presents an audit-ready dashboard. This means evidence is captured continuously as work happens, so the audit confirms an existing state rather than triggering a last-minute scramble.
Ballooning is the practice of assigning a unique number to every requirement on an engineering drawing so it can be tracked individually. Each balloon corresponds to one line on Form 3, ensuring a one-to-one mapping between drawing characteristics and their verified results. Digital ballooning in an ERP removes manual transcription and enforces that no characteristic is left unaccounted for.
A Certificate of Conformance is a supplier statement that the delivered product meets its specified requirements. An ERP can generate it automatically from the actual quality records tied to a shipment, pulling in the correct part number, revision, purchase order, and supporting certifications, so the certificate always reflects the real current configuration rather than a manually maintained template.
The most common findings are missing records, building or inspecting against the wrong drawing revision, incomplete FAIRs, broken traceability, and unresolved nonconformances. Each of these usually traces back to disconnected tools and manual handoffs rather than an inability to make good parts. Centralising the records and enforcing controls in an ERP removes the root cause.
An ERP maintains serial and lot traceability with full material genealogy, so every finished part can be tied back to its raw material heat, supplier, and certifications. If a suspect material lot is identified, the system can immediately show every part it touched. This visibility supports the AS9100 requirement to reduce the risk of counterfeit or fraudulent parts entering the supply chain.
Yes. An ERP can track which operations rely on special processes such as heat treatment, welding, or surface finishing, link them to the required process approvals and Nadcap accreditation status, and flag when a certification is approaching expiry. Because special processes cannot be fully verified by later inspection, controlling their validation and approvals in the system is essential to compliance.
Conclusion
AS9100 and AS9102 define what disciplined aerospace manufacturing looks like, but standards alone do not keep a shop compliant. The difference between a stressful audit and a routine one is whether compliance is a state you maintain or an event you prepare for. When quality gates, digital First Article Inspection, closed-loop corrective action, and end-to-end traceability are enforced by a purpose-built ERP, characteristic accountability, correct revisions, and complete records become the natural result of doing the work, not a separate burden. For aerospace and defence manufacturers in Bengaluru and beyond, that is how Elite Tech Corporation helps turn AS9100 and AS9102 from paperwork into a durable operating advantage. To see how a configured Zoho and custom AWS aerospace ERP can enforce your quality requirements continuously, talk to our team about a walkthrough tailored to your parts, processes, and audit history.Ready to run your A&D plant on one platform?
Talk to our Bangalore team, or book a free demo and see it on your own BOM.