Study for the AS9100 Lead Auditor exam by practicing three connected skills: mapping audit evidence to the correct AS9100 clause, writing nonconformity statements that state requirement, evidence, and clause without opinion, and judging corrective action adequacy and effectiveness. Work through realistic audit scenarios, compare your findings against a rubric, and refine scope decisions clause by clause.
Why AS9100 reads differently from ISO 9001:2015 when you map findings
AS9100 Rev D incorporates the ISO 9001:2015 structure and adds aerospace-specific subclauses and strengthened requirements. Your mapping task is two-layered: find the base requirement, then decide whether an aerospace addition, such as counterfeit part prevention or configuration management, applies more precisely.
The aerospace additions are not scattered; they cluster where sector risk concentrates. Clause 8.1.1 introduces operational risk management as a requirement of its own. Clause 8.1.2 addresses configuration management, and 8.1.3 production process verification, which connects directly to first article inspection practice. Clause 8.1.4 addresses prevention of use of counterfeit parts. Each addition exists because a failure mode in aerospace supply chains made the base ISO 9001 requirement insufficient on its own. When you audit, ask first which base clause the evidence touches, then whether an aerospace subclause states the same issue more specifically.
Precision in mapping matters because the clause you cite determines the corrective action an organization must design. A lapsed calibration sticker could be mapped to general monitoring resources, but the measurement traceability requirement in clause 7.1.5.2.1 addresses traceability of measurement standards and is the sharper citation. A vague citation lets the organization patch a symptom; a precise citation forces it to examine the system that allowed the condition. Practice this two-layer mapping until it is automatic, using the comparison table below as your starting reference.
| AS9100 Rev D element | Relationship to ISO 9001:2015 | Typical audit focus |
|---|---|---|
| 8.1.1 Operational risk management | New aerospace subclause within operational planning | Risk identification and control for operational processes and project decisions |
| 8.1.2 Configuration management | New aerospace subclause | Baseline control, change approval, configuration records |
| 8.1.3 Production process verification | New aerospace subclause | First article inspection, process re-verification after changes |
| 8.1.4 Prevention of use of counterfeit parts | New aerospace subclause | Supplier chain controls, part verification methods, suspect part handling |
| 7.1.5.2.1 Measurement traceability | Strengthened aerospace version of traceability of measurement results | Calibration records, traceability of standards, recall of affected measurements |
| 8.5.1.1 Control of production process | Aerospace supplementary requirement including FOD prevention | Housekeeping controls in production areas, FOD awareness, work transfers |
| 8.4.3 Information for external providers | Aerospace-specific control requirements | Special process supplier approval, delegation of verification |
Audit principles in practice: evidence-based conclusions versus personal opinion
Auditor principles include integrity, fair presentation, due professional care, confidentiality, independence, evidence-based approach, and risk-based thinking. In exam scenarios, these principles appear as decisions: what you record, how you classify it, and when you separate observation from judgment.
The evidence-based approach means every conclusion you write must trace back to something verifiable: a record, a physical condition, a measured result, or a direct statement you can attribute. Compare two statements: 'The team does not seem to care about calibration' versus 'Calibration record CR-0142 shows a due date of March; the same instrument was used on work order 5521 in May.' The first is opinion that cannot be verified or corrected; the second is evidence that can be investigated. Practice rewriting judgmental phrases into attributed facts.
Risk-based thinking shapes planning decisions rather than finding-writing. It directs where to allocate audit time: clauses and processes whose failure would most affect product safety, airworthiness, or delivery confidence get deeper sampling. This is different from evidence discipline, which governs what you record once on site. Keep the two separate in your mind. A scenario that gives you limited audit days is testing allocation reasoning; a scenario that gives you a partially completed inspection record is testing evidence handling and classification.
Building audit plans and checklists that link scope, criteria, and AS9100 clauses
Effective preparation means defining audit scope, criteria, and objectives before drafting checklists, then building checklist items that map each AS9100 requirement to the records and process elements that would demonstrate conformity.
Scope defines which sites, processes, and activities are covered; criteria define the requirements against which conformity is judged, here the AS9100 standard plus the organization's own documented system. Confusing these is a common planning error: writing a checklist question such as 'Does the plant follow good practice?' embeds an undefined criterion. Instead, write 'Does the organization maintain documented information on traceability as required by 8.5.2, and can it retrieve records for a sampled serial number within its stated timeframe?' The requirement and the test are explicit.
A practical drafting method: for each clause in your assigned scope, list the documented information the clause expects, the process owners responsible, and the physical or system evidence that would confirm implementation. Then add sampling logic. Audits sample; they cannot verify every transaction. Decide in planning what sample size and selection basis you will use so that your conclusions remain defensible. A checklist built this way also becomes your study tool, because drafting it forces you to reread each aerospace subclause and ask what conformity actually looks like.
Conducting the audit: tracing a serial number from sales to shipped product
On-site audit work is structured around evidence trails. The most instructive exercise for AS9100 scope is a trace exercise: pick one product serial number and follow it through order entry, production, inspection, and shipment, checking each aerospace-required record at each step.
The trace exercise exposes system weaknesses that document review alone misses. Take a serial number and request the contract review record, the configuration baseline under 8.1.2, the traveler or routing, calibration records of instruments used, special process certificates from external providers, first article inspection results under 8.1.3, and the nonconforming product log if any step raised an issue. Each handoff is a chance to verify that 8.5.2 identification and traceability records actually link, that configuration management kept the built configuration aligned with the approved baseline, and that externally provided processes carry current approvals.
Interview technique interacts with the trace. Open questions such as 'Walk me through what happens when this measurement fails' elicit the real process; closed questions confirm specific facts you then record. Record both conformity and nonconformity evidence, because the balance of evidence supports your overall conclusion. If a trace stops at a missing link, note the exact records you requested, who you requested them from, and the response received. That discipline is what turns a nagging impression into a raisable finding later.
Writing the nonconformity: worked scenario on lapsed calibration and product recall
A well-written nonconformity statement has three parts: the requirement including its clause, the objective evidence, and a clear statement of the gap. The clause chosen and the scope stated determine the corrective action the organization must perform.
Worked scenario 1. During a production audit you see a CMM inspection record signed yesterday. The instrument's calibration label expired two months ago. A weaker response writes: 'Minor NC against clause 7.1.5, calibrate equipment more promptly.' This version is weak in three ways: the clause is imprecise, the scope covers only the label, and no consequence is explored. The better statement cites 7.1.5.2.1, states the requirement that measuring equipment be calibrated with traceable results, presents the evidence of the expired label and the dated inspection record, and then extends the audit: which parts were inspected with this instrument during the lapse, and are those parts subject to control of nonconforming outputs under clause 8.7?
The reason this matters is causal, not stylistic. If you scope the finding to a label, the organization re-labels the instrument and nothing changes. If you scope it to the measurement traceability system, the organization must determine the calibration lapse interval, identify affected product, and address it. Note the distinction between the nonconformity itself and the product consequence: product disposition follows 8.7 processes, while the management system cause is addressed through 10.2 corrective action. Practice writing both the NC statement and the follow-up questions for every scenario you study.
Grading findings and evaluating corrective action: worked scenario on an expired special process supplier
Finding classification reflects whether the gap is isolated or systemic and whether product conformity is affected. Corrective action evaluation checks root cause analysis, action scope, and evidence of effectiveness, not just the existence of a completed form.
Worked scenario 2. You find that work orders were released to an anodizing supplier whose entry on the approved supplier list lapsed last year, with no re-evaluation on file. A plausible mistake is recording this as an opportunity for improvement phrased as 'supplier management could be strengthened.' That classification abandons the evidence. The better decision is a nonconformity against clause 8.4 and its aerospace controls for externally provided processes, stating the lapsed approval, the specific purchase orders released during the lapse, and the special process nature of the work. Whether it is graded as isolated or systemic depends on what sampling shows: one lapse among a current list suggests a localized failure; repeated expired approvals suggest the approval monitoring system itself is not functioning.
When the organization responds, evaluate the corrective action against the same logic. A response consisting of 'the supplier's approval was renewed and staff were retrained' addresses neither cause nor effectiveness. Ask: why did an expired approval allow purchase orders to release, what system should have blocked or flagged it, what evidence shows the blocking now works, and were products processed during the lapse assessed for conformity? Retraining alone is rarely sufficient because it addresses the individual rather than the system condition that permitted the lapse. Effectiveness verification means checking subsequent performance, such as later approvals and releases, not merely accepting the action plan.
A preparation sequence and readiness rubric you can adapt
Build study around cycles of reading clauses, drafting checklists, and writing findings from scenarios, then score your own work against a rubric. Readiness means your findings survive a critical review of clause, evidence, scope, and classification.
A realistic sequence: first pass through AS9100 clause by clause, marking the aerospace additions against the ISO 9001:2015 base structure. Second, draft checklists for your strongest scope areas as described in the planning section. Third, work written audit scenarios daily: read the scenario, write the finding, then compare against the rubric below. Fourth, practice corrective action evaluation separately, judging sample responses for root cause and effectiveness. Fifth, run a timed full simulation combining planning, a scenario trace, and finding-writing. Adjust the length of each phase to your available weeks; the order matters more than the duration because each phase builds on the prior one.
Use this self-check rubric when reviewing each finding you write. Score your own work honestly; treat the rubric as a learning milestone, not a prediction of any exam outcome. When a finding scores below the mark on any row, return to the relevant clause and rewrite rather than moving on. Pair this sequence with the free practice questions on this site to test recall under time conditions after the writing skills are in place.
- Clause precision: does the cited clause state the requirement more specifically than any alternative clause would?
- Evidence quality: is every factual claim traceable to a record, observation, or attributed statement?
- Scope: does the finding cover the system condition and affected product, not just the symptom observed?
- Classification: is the isolated-versus-systemic judgment supported by sampling evidence described in the finding?
- No opinion: have judgmental words such as 'poor', 'weak', or 'ignored' been removed from the statement?
- Follow-up logic: can you state what corrective action and effectiveness evidence the finding should drive?
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.