A clause-by-clause breakdown of what your aerospace QMS documentation needs — and where most suppliers fall short
Affiliate Disclosure: Some links in this article are affiliate links. If you purchase through them, The Standards Navigator may earn a commission at no additional cost to you.
The Documentation Gap That Fails Aerospace Audits
AS9100 documentation requirements cover the documented information needed to operate and demonstrate an aerospace QMS, along with aerospace-specific records and controls in areas such as configuration management, traceability, counterfeit parts prevention, first article inspection, and FOD control. The exact documents and records an organization maintains depend on its processes, applicable requirements, and customer flow-downs.
AS9100 documentation isn’t ISO 9001 paperwork with an aerospace label stuck on it. Traceability records, first article inspection (FAI) data, and configuration management records aren’t background paperwork — auditors use them as objective evidence that aerospace parts were manufactured and controlled according to applicable requirements.
Most suppliers assume a quality manual and a stack of procedures covers it. Then an auditor selects a part number, asks for the traceability record behind its FAI, and finds the two don’t connect — what looked like a minor gap becomes a major nonconformance.
Whether you’re mapping documentation before your first Stage 1 audit or checking an existing system against Rev D, this breaks down exactly what auditors pull first — and where the gaps usually are.
FROM THE SHOP FLOOR: I’ve sat across the table from an AS9100 auditor who skipped the quality manual entirely and went straight for first article inspection records on a part we’d shipped eight months earlier. We had the FAI — what we didn’t have was the linked traceability record showing which material heat lot went into it. That gap alone became a major finding. Auditors aren’t grading your paperwork; they’re testing whether your records actually trace back to the part in front of them.
👉 Most AS9100 documentation gaps don’t surface until an auditor asks for a specific record — by then it’s too late to fix quietly. Run the AS9100 Rev D Gap Assessment Checklist before your next audit and find out exactly where your documentation stands.
In this guide:
- What AS9100 documented information actually requires — and where it goes beyond ISO 9001
- Whether you still need a quality manual under Rev D
- The core records auditors pull first: FAI, traceability, counterfeit parts, FOD
- Two documentation areas most suppliers underbuild
- Common findings and how to close them before your audit
- Where to buy the standard and find training if you’re building this from scratch
Table of Contents
👉 Start Here
- Buy the AS9100 Rev D Standard — ANSI Webstore — the current edition, direct from the authorized source. Use code CC2026 for 5% off through December 31, 2026.
- AS9100 Training — BSI Group — covers documentation requirements clause by clause if you’re building this system without a consultant.
- AS9100 Rev D Gap Assessment Checklist — free 74-item clause-by-clause checklist.
What “Documented Information” Actually Means Under AS9100
AS9100 Rev D uses the same “documented information” language as ISO 9001 — but the aerospace-specific clauses layer on requirements that don’t exist in a standard ISO 9001 system at all.
AS9100 Rev D does not explicitly require a document called a quality manual. The practical takeaway is that eliminating a document called a “quality manual” does not eliminate the need to document and communicate how your QMS is structured.
Many aerospace organizations continue to use a quality manual because it provides a practical way to describe the QMS and its relationship to the applicable requirements — and it’s the document reviewers commonly use to navigate everything else.
Where AS9100 genuinely goes further than ISO 9001 is in the aerospace-specific documented information requirements: first article inspection, more extensive material and process traceability, counterfeit parts prevention, foreign object debris (FOD) control, and configuration management. None of these have a real equivalent in a baseline ISO 9001 system — see What Is AS9100? for the full standard overview if you’re still mapping out scope.
If you’re building this documentation structure from scratch rather than adapting an existing ISO 9001 system, the ISO Documentation Kits for Manufacturers page is a reasonable starting point for the underlying procedures and forms — just plan to adapt anything generic to AS9100’s aerospace-specific requirements before relying on it for certification.
The Core Records Auditors Pull First
First Article Inspection Records
A common audit approach is to select a specific part number and request the FAI record supporting it, along with the traceability behind it. FAI reporting itself is governed by AS9102, published by SAE International. Full requirements — including what counts as a valid FAI and when a re-FAI is triggered — are covered in First Article Inspection Requirements.
Traceability Records
Traceability records should allow applicable material, batch/lot, and process information to be traced through the product lifecycle to the shipped part, based on the organization’s processes and applicable requirements — not just exist as separate records. See AS9100 Traceability Requirements for what Clause 8.5.2 actually demands.
Counterfeit Parts Prevention Records
Documented controls for counterfeit parts prevention are required under Clause 8.1.4 — and auditors check whether they’re actually followed, not just written. Full breakdown in AS9100 Counterfeit Parts Standards.
FOD Control Records
AS9100 expects documented controls and evidence appropriate to the organization’s processes for preventing foreign object debris — the specific form that takes varies by operation. See FOD Control Standards for what Clause 8.5.4 requires.
A recurring pattern I’ve seen: these four record types exist independently but aren’t cross-referenced. An auditor pulls an FAI, asks for the traceability record behind it, and finds no clear link between the two documents — even though both technically exist. In practice, that kind of disconnect often draws more scrutiny than a missing document, because it suggests the system isn’t actually being used to trace parts, just to generate paperwork.
The Audit Trail: Part Number → Revision → Material Lot → Process Route → FAI → Final Record
An auditor doesn’t just want to see that each record in that chain exists individually. They want to see how the records relate to each other and to the specific part in front of them. (This makes a strong visual for the published page — worth building as a simple graphic rather than just text.)
👉 If your traceability records and FAI paperwork don’t reference each other by part number and revision, that’s a gap worth closing before an audit tests it. Download the Manufacturing Compliance Checklist and confirm your records connect.
Two Documentation Areas Most Suppliers Underbuild
Configuration Management Documentation (Clause 8.1.2)
Configuration management — tracking exactly which design revision, engineering change, and customer-approved deviation applies to a given part — gets far less attention than FAI or traceability, but auditors increasingly check it as a standalone item. If your documentation doesn’t clearly show which configuration was in effect at the time of manufacture, that’s a gap worth closing before it becomes a finding. This is dense enough to deserve its own dedicated breakdown — flagging it here as a topic to watch.
Risk-Based Documentation for Special Processes
Special processes — such as welding, heat treating, and nondestructive testing — carry their own documented risk requirements under AS9100’s risk-based thinking clauses. Nadcap accreditation may apply separately when required by a customer or applicable supply-chain requirements; that accreditation question is covered in NADCAP vs AS9100. The documentation angle specifically — how you document special-process risk decisions, distinct from whether you’re Nadcap-accredited — is underserved content-wise and worth a dedicated piece.
How AS9100 Documentation Differs from ISO 9001
| Category | ISO 9001 | AS9100 |
|---|---|---|
| Quality Manual | Not explicitly mandated | Not explicitly mandated, but commonly used in practice |
| First Article Inspection | No aerospace-specific FAI requirement | Incorporated through AS9100 and applicable customer requirements; AS9102 (SAE) governs FAI reporting |
| Traceability | General requirement, scope flexible | More extensive material/process traceability, including customer- and product-specific requirements where applicable |
| Counterfeit Parts Prevention | No equivalent requirement | Documented controls required (Clause 8.1.4) |
| Configuration Management | No equivalent requirement | Required (Clause 8.1.2) |
| FOD Control | No equivalent requirement | Documented controls and evidence appropriate to the organization’s processes and applicable requirements |
For the full standard-by-standard comparison beyond documentation specifically, see AS9100 vs ISO 9001.
👉 Building this documentation structure without a consultant is realistic — but only if you’re working from the current edition. Buy the AS9100 Rev D standard through ANSI Webstore and use code CC2026 for 5% off.
What Happens When Documentation Doesn’t Hold Up
A documentation gap doesn’t automatically fail an audit — but an auditor who finds one disconnected record set often digs deeper, and what started as a single finding turns into a pattern of findings across the whole system. That’s the real cost: not the first gap, but what it triggers.
The cost objection: it’s fair to wonder whether this level of documentation rigor is overkill for a small shop with a handful of part numbers. When FAI and traceability requirements apply, a five-person shop and a five-hundred-person supplier may need to maintain the same core record types for a given part number; the difference is the complexity of the system used to manage them.
If you’re deciding whether your existing system is ready, AS9100 Internal Audit Process walks through running that check yourself before a registrar does it for you. And if you haven’t picked a certification body yet, AS9100 Certification Bodies — Ranked & Reviewed is a good next stop — worth confirming the body you choose is itself accredited by a recognized accreditor such as ANAB.
In practice, traceability is a significant part of aerospace QMS auditing because auditors need objective evidence that product and process records can be connected to the requirements they support.
Quick Documentation Checklist
✅ Quality manual (or equivalent scope document) references all applicable Rev D clauses
✅ FAI records exist and cross-reference traceability records by part number and revision
✅ Traceability records identify applicable material heat/lot/batch information for shipped parts, based on customer, product, and process requirements
✅ Documented controls for counterfeit parts prevention are in place and actively followed, not just written
✅ FOD controls are documented and supported by evidence appropriate to the organization’s processes and applicable requirements
✅ Configuration management records show which design revision applied at time of manufacture
✅ Special process records (welding, heat treat, NDT, etc.) are retained per customer and registrar requirements
FAQ
Is a quality manual required under AS9100 Rev D?
Not explicitly by the standard’s own wording — but many aerospace organizations continue to use one because it provides a practical way to describe the QMS and map it to the standard’s structure. Skipping it entirely can create more audit friction than it saves in paperwork, since certification bodies commonly expect some document that fills that role.
What documents does an AS9100 auditor ask for first?
A common audit approach is to select a specific part number and request the first article inspection record supporting it, followed by the traceability record behind that FAI. Auditors use this pairing to test whether your documentation system actually connects, not just exists.
What’s the difference between documented information and records under AS9100?
Documented information is the broader AS9100 term covering anything required to be created, maintained, and controlled — procedures, work instructions, and forms all count. Records are a specific type of documented information that provide evidence of results, like a completed FAI or a calibration record. Every record is documented information, but not everything documented is a record.
How long do AS9100 records need to be retained?
Retention periods vary by customer contract and registrar requirement rather than a single fixed AS9100 rule — many aerospace customers require retention well beyond typical ISO 9001 timeframes, sometimes for the life of the program. Check your specific customer flow-down requirements rather than assuming a default period applies.
Do I need separate documentation for each customer?
Not necessarily separate systems, but you likely need customer-specific supplemental requirements layered onto your core AS9100 documentation — most aerospace OEMs have their own flow-down requirements beyond the base standard.
What is a common AS9100 documentation finding?
One recurring documentation problem is records that exist individually but aren’t cross-referenced — an FAI with no linked traceability record, or a traceability record that doesn’t tie back to the part it supports. The documents technically exist; they just don’t function as a connected system.
Can I use the same documentation system for ISO 9001 and AS9100?
Largely yes for the shared core structure, but AS9100-specific records (FAI, counterfeit parts prevention, configuration management, FOD control) have no ISO 9001 equivalent and need to be built as additions, not substitutions.
Do I need software to manage AS9100 documentation, or can spreadsheets work?
Spreadsheets can work for a small shop with limited part numbers, but the risk grows with volume — the more parts and revisions you’re tracking, the easier it becomes for records to silently disconnect from each other, which is the exact failure pattern auditors catch most often.
How much documentation does a small aerospace supplier actually need?
The same core record types as a larger supplier — a small shop doesn’t get a reduced list of required records. What differs is the complexity of the system used to manage them; a simpler operation can often meet the same requirements with a leaner, more manual system than a high-volume supplier needs.
📥 Free Resources
- AS9100 Rev D Gap Assessment Checklist — 74-item clause-by-clause checklist for aerospace suppliers assessing their QMS before certification
- ISO 13485 Gap Assessment Checklist — free checklist for medical device manufacturers assessing their QMS against ISO 13485 requirements
- ISO 9001 Roadmap — step-by-step implementation guide for manufacturers building or improving a quality management system
- Manufacturing Compliance Checklist — practical compliance reference covering key ISO, OSHA, and quality requirements for production environments
- Supplier Quality Checklist — evaluation tool for assessing supplier quality controls and flow-down compliance before audits or new contracts
Not Sure What to Do Next?
🔹 Still researching what AS9100 documentation actually requires? Start with What Is AS9100? for the full standard overview.
🔹 Ready to build your documentation structure? Buy the current AS9100 Rev D standard through ANSI Webstore — you can’t build compliant documentation from an outdated edition.
🔹 Need training to get your team up to speed? BSI Group’s AS9100 training courses cover documentation requirements clause by clause.
🔹 Want a professional gap assessment first? Download the free AS9100 Rev D Gap Assessment Checklist.
Documentation is where AS9100 audits are actually won or lost — not in the quality manual, but in whether your records connect to the parts they’re supposed to trace. Get the structure right from the beginning, and maintaining audit-ready evidence becomes far easier. That’s the standard The Standards Navigator holds every AS9100 guide to.
Stay Ahead of Your Next AS9100 Audit
Most aerospace suppliers don’t fail audits because they lack documentation — they fail because their documentation doesn’t connect. FAI records that don’t reference traceability. Traceability that doesn’t tie to configuration. Individually complete, collectively disconnected.
Suppliers who struggle treat documentation as a checklist exercise, built once and left alone. Suppliers who succeed build cross-referencing into every record from day one, so nothing has to be reconstructed under audit pressure.
The Standards Navigator covers AS9100 implementation for aerospace suppliers building audit-ready quality systems from the ground up.
👉 Get updates on AS9100 and aerospace compliance
👉 Be first to access new gap assessment checklists and documentation templates
Industrial Compliance. Clearly Explained.
