AS9100 treats root cause corrective action as a formal, risk‑based, and evidence‑driven requirement beyond the baseline of ISO 9001: it mandates documented root‑cause analysis, actions to address systemic and supplier‑related causes, and documented verification of effectiveness with explicit emphasis on product safety and the prevention of recurrence. The standard tightens expectations for control of nonconforming outputs, supplier oversight, and traceability, and requires organizations to consider safety, reliability, and regulatory reporting when defining corrective actions and validating their outcomes.
For EHS professionals this difference is consequential: incomplete or superficial corrective actions can leave latent hazards unaddressed, increasing the likelihood of serious incidents, regulatory enforcement, costly recalls, or loss of certification by aviation and safety authorities. Effective AS9100 compliance requires cross‑functional investigation that ties human factors, process controls (for example LOTO and confined‑space procedures), design and supplier issues, and verification evidence into a single, auditable record. Managing that volume of documentation, structured workflows, supplier follow‑up, and evidence of effectiveness at enterprise scale is most feasible with an integrated EHS/QMS platform; Simple But Needed (SBN) is designed to centralize nonconformance records, RCA workflows, corrective‑action verifications, and supplier controls to support sustained AS9100 compliance.
How does AS9100 require root cause analysis and corrective action differently than ISO 9001
AS9100 is built on ISO 9001:2015 (see ISO 9001 clause 10.2, Nonconformity and corrective action) but adds aerospace-specific expectations that raise the bar on depth, traceability and product-safety focus of root cause analyses (RCAs). Where ISO 9001 requires an organization to determine causes and implement corrective actions “as appropriate,” AS9100 explicitly requires organizations to treat product-safety and safety‑critical nonconformities with higher rigor — i.e., RCAs must address latent system causes (design, process, supplier controls and human factors) and provide demonstrable links between corrective actions and prevention of recurrence for flight‑safety or airworthiness items. In practice auditors and OEMs expect documented linkage from the nonconformance through containment, detailed causal analysis, corrective action, verification and sign‑off with traceability to lot/batch and serial numbers.
Practically that means depth and evidence differ. For a torque/installation nonconformance on a flight‑critical fastener — e.g., torque recorded 15% outside specified N·m tolerance — ISO 9001 might accept a corrective action that updates the inspection frequency; AS9100 expects documented containment (quarantine and 100% inspection), an RCA that examines tooling calibration intervals, operator training, work instruction clarity and supplier material certification, and a verification plan. Measurements and controls are typical: torque tools calibrated to ISO/IEC 17025 intervals (commonly 12 months or per OEM requirement), inspection reports that include measured N·m values, and rework instructions with objective acceptance criteria. AS9100 places emphasis on preserving objective evidence (calibration certificates, captured torque readings, operator signatures) in the corrective action record.
Timeframes and acceptance criteria for corrective action under AS9100 are more prescriptive in supply chains even if not written as a single numeric clause in the standard. Aerospace customers and certification auditors commonly expect containment actions within 24–72 hours for safety‑critical issues, a documented corrective action plan with milestones (often submitted within 5–10 business days), RCA completed within 30 calendar days, and effectiveness verification performed within 60–90 days after implementation before resuming normal production or shipment. Where corrective actions intersect process‑safety hazards, OSHA’s Process Safety Management standard (29 CFR 1910.119(m)) also applies: incidents that resulted in, or could have reasonably resulted in, a catastrophic release must be investigated and corrective actions implemented and documented so they eliminate root causes and prevent recurrence.
Simple But Needed (SBN) operationalizes these AS9100 expectations through its CAPA and incident‑tracking modules. SBN CAPA lets teams create a corrective action record tied to the originating incident, require RCA inputs (5‑Why/8‑D fields), attach objective evidence (calibration certificates, torque tool logs in N·m), set milestone dates (containment: 24–72 hrs, RCA: 30 days, verification: 60–90 days), and escalate to supplier CAPA with mandatory supplier responses. SBN’s audit and inspection features link inspections (e.g., incoming fastener lot inspection, tool calibration checks) to CAPAs, enforce signoffs, and produce audit‑ready reports showing linkage from nonconformance → RCA → corrective action → effectiveness verification for AS9100 certification evidence.
What evidence and documented controls does AS9100 expect to demonstrate effectiveness of corrective actions
AS9100D adopts ISO 9001:2015 corrective action requirements (clause 10.2) but places explicit expectation that organizations retain documented information showing the nature of nonconformities, actions taken, results of the actions, and evaluation of effectiveness — including any updates to risk assessments and the quality management system. For aerospace suppliers this typically means a written root‑cause report (8D, 5‑Why or equivalent) that lists chronology, containment actions, proposed permanent corrective actions, responsible owners and planned completion dates; audit teams will expect to see the date stamped records and signature approvals tied to the nonconformance record (e.g., NCR number, work order or lot number) so the corrective action trail is auditable to product and lot traceability.
AS9100 auditors and primes expect objective verification and validation evidence rather than narratives alone. Acceptable evidence includes first article inspection (FAI) forms (AS9102 format where required by contract), SPC charts showing pre‑ and post‑action control limits with Cpk/Cp calculations, measurement system analysis (gauge R&R) results, and rework/retest reports showing sample sizes and acceptance criteria. Industry practice in aerospace is to show containment within 24–72 hours for high‑severity failures, a documented CAPA plan implemented within 30 days for most major nonconformances, and verification/validation of effectiveness at 30, 60 and 90 days (or at a production volume milestone) with quantitative metrics such as PPM trend lines or defect counts per 1,000 parts — AS9100 itself does not specify these exact timeframes, but auditors will judge whether the chosen timeframe is commensurate with product safety risk.
When corrective actions intersect with worker safety controls, AS9100 evidence expectations must be cross‑mapped to OSHA regulatory requirements. For example, a corrective action that changes lockout/tagout procedures must show updated written procedures, training records and the results of the required annual LOTO inspections under 29 CFR 1910.147(c)(6)(iii); a corrective action involving confined space entry must document permit revisions, rescue capability evidence and retraining per 29 CFR 1910.146(d) and associated entry permits; respiratory protection changes must include fit‑test records and annual training as required by 29 CFR 1910.134(e). Auditors will look for documentary proof that the corrective action both resolved the product/process nonconformity and preserved or improved compliance with applicable OSHA requirements.
To operationalize these expectations and keep corrective actions auditable to AS9100 clause 10.2, Simple But Needed (SBN) provides a CAPA module that links NCRs/incident records to root‑cause fields, containment steps, assigned owners, and timebound actions, and stores verification evidence (inspection photos, AS9102 forms, SPC chart uploads, gauge R&R reports). SBN’s incident‑tracking and audit modules automatically generate reminders for 30/60/90‑day verifications, map corrective actions to specific clauses (e.g., 10.2, 8.7), and tie records to LOTO, confined space, JHA or chemical inventory entries so auditors can pull a single evidence package showing the nonconformance, the risk assessment update, documented controls and measured effectiveness metrics.
How must corrective actions be integrated with risk management and occupational health and safety systems under AS9100
AS9100 (aligned with ISO 9001:2015) requires that corrective actions are driven by and tied back to the organization’s risk management processes (see ISO/AS clause 6.1 on actions to address risks and opportunities and clause 10.2 on nonconformity and corrective action). Practically, that means an RCA that leads to a corrective action must record the risk assessment inputs (e.g., updated FMEA severity/occurrence ratings, process capability Cpk values) and document how the action reduces the quantified risk. While AS9100 does not mandate specific deadlines, aerospace supply chain practice typically expects immediate containment within 24–48 hours for safety- or flight-critical events, a documented root cause analysis within 30–60 days, and verified corrective actions completed and measured for effectiveness within 90–180 days — your CAPA records should reflect those timelines and link back to the original risk scoring.
Corrective actions under AS9100 must explicitly consider occupational health and safety hazards that intersect with product nonconformities. For example, if an assembly nonconformance creates a potential for dropped objects or pinch points, the corrective action must address both product conformity and OHS controls (e.g., update the JHA and LOTO procedures under 29 CFR 1910.147, revise confined-space entries per 29 CFR 1910.146 if applicable, and update HazCom per 29 CFR 1910.1200). Effectiveness metrics should include both quality measures (PPM or DPMO, Cpk) and safety metrics (TRIR/DART per OSHA recordkeeping 29 CFR 1904) tracked over a 6–12 month window to demonstrate that the action reduced both defect recurrence and injury risk.
AS9100 expects documented controls that show prevention and verification: revised control plans, process work instructions, PFMEAs, verification samples (typical practice is three consecutive acceptable production lots or a 6-month data window), and internal-audit evidence that the change is embedded. Those records should include objective evidence — measurement results that demonstrate Cpk improvements to target (commonly ≥1.33 for critical characteristics), inspection records with measured dimensions to specified tolerances, and signed verifier checklists. To capture and connect those artifacts in a single workflow, the organization should use inspection and CAPA linkage so an inspection finding automatically generates a corrective action and attaches measurement evidence; SBN’s inspection capabilities make it straightforward to link inspection records to CAPA and audit trails using the SBN Inspections software.
Integrating corrective actions with supplier management and the broader EHS program is also an AS9100 expectation: corrective actions that affect supplier processes must be flowed down in purchasing documents, tracked to supplier verification (typical supplier response times are 30 days for containment, 60–90 days for root cause actions, and verification over 3 production lots or 180 days), and tied into site-level safety programs (e.g., supplier CAPAs that require changes to on-site LOTO permits or JHAs). SBN helps operationalize that linkage by providing CAPA tracking tied to audits and supplier records, incident tracking that feeds into supplier performance dashboards, and audit modules that record supplier verification evidence — enabling safety teams to manage supplier corrective action status, assign verification owners, and produce the AS9100 evidence trail auditors expect.
What are AS9100 expectations for supplier corrective action and flow-down to subcontractors in safety-critical operations
AS9100D augments ISO 9001:2015 clause 8.4 (Control of externally provided processes, products and services) by requiring organizations to explicitly flow-down requirements for product safety, critical characteristics and verification activities to external providers; in practice this means contracts and purchase orders must call out AS9102 First Article Inspection (FAI) obligations, NADCAP or equivalent accreditation for special processes (e.g., heat treat, coatings, NDT) and rights of access for source inspection and audit. Aerospace suppliers are routinely required to maintain traceability records (batch/serial level) and maintain records for the customer-specified retention period (commonly 7–10 years for airworthiness-related items), and AS9100 auditors will expect documented evidence that those flow-downs were executed and monitored.
When a supplier nonconformance affects a safety-critical characteristic the expectation under AS9100 and ISO 9001:2015 clause 10.2 is immediate containment plus documented corrective action and verification of effectiveness; industry-standard timetables used by aerospace primes (and routinely reviewed in audits) include containment within 24–72 hours of discovery, a formal Supplier Corrective Action Request (SCAR) submitted within 5–10 business days, and objective verification of effectiveness within 30–90 days or by the next affected production lot. Measurable acceptance criteria are customary—e.g., reduction of defect rate to below the contract PPM threshold (often specified as ≤50–100 PPM depending on the commodity) or three consecutive production lots meeting acceptance—rather than open-ended or purely subjective closure criteria.
For safety-critical work the flow-down must also incorporate statutory and regulatory safety requirements so that subcontractors are contractually bound to comply with applicable OSHA standards and consensus codes; typical contractual clauses require compliance with 29 CFR 1910.119 (Process Safety Management) where applicable, 29 CFR 1910.147 (control of hazardous energy/LOTO) for maintenance on powered equipment, and 29 CFR 1910.146 for permit-required confined spaces when those hazards exist. In practice primes require suppliers to demonstrate personnel qualifications (e.g., NDT personnel per NAS 410 or welders qualified to ASME/AWS standards), maintain written LOTO and confined-space procedures, and provide evidence (training records, procedures, PT/UT reports) during supplier surveillance or source inspection to satisfy AS9100 product-safety expectations.
Auditors evaluating supplier corrective action and flow-down will look for an end-to-end compliance trail: contractual flow-down language, supplier performance data (PPM, on-time delivery, backlog), documented SCAR with contained product segregation, root-cause analysis (8D or documented 5-Why with supporting data), verification records (inspection reports, rework dispositions, FAI results) and management-review inputs showing trend analysis. AS9100 certification audits expect the organization to demonstrate closed-loop management of supplier CAPAs and to show how supplier CAPA outcomes are incorporated into risk registers and production controls; SBN’s CAPA and supplier-audit workflows integrate SCAR issuance, evidence upload, supplier performance dashboards and audit scheduling so safety teams can assign SCARs, track containment and verification dates, and produce the documentary trail required for AS9100 supplier oversight.
How do auditors assess root cause investigations and corrective action effectiveness during AS9100 certification audits
Auditors begin by verifying conformance to AS9100D clause 10.2 (Nonconformity and corrective action) and related requirements (9.1 monitoring, 9.2 internal audit, 7.1.5.2 measurement traceability). They expect documented root-cause methodology (5‑Why, Fishbone, FMEA) with evidence that the chosen method is appropriate to the failure mode and that personnel performing the analysis are qualified and trained; competence records and training matrices are reviewed against the corrective action file. Auditors will confirm that measurement devices cited in the investigation are calibration-traceable per 7.1.5.2 and check calibration stickers, calibration certificates, and MSA records to ensure data used in the RCA are valid — this is why CAPA records that attach calibration certificates are commonly requested and reviewed in audits by evidence sampling. SBN’s CAPA module centralizes RCA records, qualifications, and calibration attachments so teams can present a single, auditable corrective-action trail during certification reviews.
While AS9100D does not prescribe absolute timeframes for containment and root-cause closure, auditors assess timeliness relative to risk: for safety‑critical nonconformances OEMs and primes commonly expect initial containment within 48–72 hours, documented root cause within 30 days, and permanent corrective action implemented and verified within 90 days. Auditors will therefore look for interim containment evidence (hold notices, quarantine tags, blocked inventory counts) and chronological action logs showing prompt escalation when the event impacted product conformity or safety. They also examine links between the corrective action and occupational safety controls where applicable (for example, LOTO per OSHA 29 CFR 1910.147 or confined-space controls per 29 CFR 1910.146) to ensure temporary fixes did not introduce new hazards. SBN’s incident-tracking and containment workflows log timestamps, quarantine counts, and link to LOTO and confined‑space permits so auditors can readily confirm timely containment and escalation steps.
Effectiveness verification is judged on measurable reduction of the problem and verification methods used: auditors expect objective evidence such as SPC charts, before/after defect rates in DPPM or PPM, trending over at least one product life cycle or 3–12 months where applicable, and internal-audit follow-up (clause 9.2) demonstrating no recurrence. Typical acceptance criteria examined include reduction from a pre‑CAPA DPPM to a target DPPM (for example, from 5,000 PPM to <50 PPM) or statistically significant process capability improvements (Cpk >1.33) demonstrated via control charts. Auditors will also review verification activities to ensure they were independent of those who implemented the fix and that validation covered production-normal conditions (e.g., full shift runs, environmental ranges). SBN’s audits module and SPC-enabled dashboards facilitate storing pre/post metrics, internal-audit follow-ups, and independent verification evidence so teams can demonstrate sustained effectiveness.
For supplier-related findings auditors focus on flow‑down and closure evidence under AS9100D clause 8.4 (control of externally provided processes, products and services) and 8.7 (nonconforming outputs), expecting supplier CAPAs, SCARs, performance scorecards, and on‑site verification where the supplier’s corrective actions affected safety‑critical hardware or processes. They will check contractual flow‑down (purchase orders or supplier quality requirements), supplier training records, and evidence that supplier fixes were verified at the receiving site (incoming inspection data, FAI results, or on‑site audit reports). When corrective actions require equipment changes that affect safety procedures, auditors verify coordination with OH&S controls (for example, that LOTO procedures per 29 CFR 1910.147 and confined-space re‑assessments per 29 CFR 1910.146 were updated and applied). SBN’s supplier CAPA and procurement-linked CAPA features let organizations attach SCARs, supplier verification reports, and purchase‑order flow‑down evidence to each corrective action file for auditor review.
Frequently Asked Questions
How does AS9100 treat root cause corrective action differently than ISO 9001 for safety‑critical failures?
AS9100 requires documented RCAs that probe latent system causes (design, process controls, human factors and supplier issues) and ties containment → RCA → permanent action → verification to lot/serial traceability, with auditors expecting evidence focused on product safety. Industry practice is containment within 24–72 hours, RCA completed within ~30 days, and effectiveness verified within 60–90 days; SBN’s CAPA and incident‑tracking modules link the NCR to RCA fields, attach calibration/inspection evidence, and record timestamps for auditability.
What objective evidence will auditors accept to demonstrate corrective action effectiveness under AS9100?
Auditors expect objective artifacts such as AS9102 FAI forms, SPC control charts showing before/after Cpk improvements (commonly target ≥1.33 for critical characteristics), gauge R&R/MRA results, calibration certificates (ISO/IEC 17025 traceability), and signed verification reports rather than narrative-only closure. When actions affect safety controls, documentary proof must also show updated procedures and training per OSHA (e.g., LOTO records per 29 CFR 1910.147); SBN’s CAPA and inspections features let teams attach AS9102s, SPC uploads, calibration certs and LOTO/confined‑space evidence into the corrective‑action file.
What timelines and measurable acceptance criteria should we use for CAPAs to satisfy aerospace customers and auditors?
Typical aerospace expectations are containment within 24–72 hours for safety‑critical issues, a formal SCAR submitted within 5–10 business days, RCA within ~30 days, and verified effectiveness within 60–90 days or by three consecutive acceptable production lots (or 180 days) — measurable criteria commonly include PPM/DPPM reduction to contract thresholds (often ≤50–100 PPM) or Cpk ≥1.33. SBN’s CAPA module enforces milestone dates, automated reminders, and tracks verification evidence and SPC metrics so teams can show timeliness and objective acceptance criteria during audits.
How must corrective actions interact with occupational safety controls like LOTO and confined‑space procedures under AS9100?
Corrective actions must explicitly address OHS hazards that intersect product nonconformities and document updates to written programs, training and verification per OSHA (e.g., LOTO per 29 CFR 1910.147, confined‑space permit and rescue evidence per 29 CFR 1910.146, respirator fit‑tests per 29 CFR 1910.134). Effectiveness should be tracked with both quality metrics (PPM, Cpk) and safety metrics (TRIR/DART over a 6–12 month window); SBN links CAPA records to LOTO, confined‑space, JHA and training records so safety teams can produce a single auditable package showing both product and safety remediation.
What do auditors look for when assessing supplier corrective actions and flow‑downs for safety‑critical subcontractors?
Auditors expect contractual flow‑downs that call out product‑safety requirements, SCARs with containment (24–72 hours), RCA and supplier action plans (SCAR within 5–10 business days, RCA ~30 days), and supplier verification evidence such as incoming inspection/FAI results, on‑site audit reports or three acceptable production lots/defined PPM targets. Evidence of purchase‑order flow‑down, supplier CAPA closure, and linkage to site risk registers is required; SBN’s supplier CAPA, procurement‑linked CAPA and supplier performance dashboards centralize SCAR issuance, verification uploads and audit scheduling for auditor review.
Simple But Needed (SBN) is a global EHS platform that provides industries such as Oil & Gas, Insurance, Government and Public Entities, Utilities, Pharma and Biotech Laboratories, Education, Manufacturing, Food and Beverage, Healthcare and Construction with a simple yet powerful tool to manage all of their EHS needs. We handle Inspections, LOTO procedures, complex Chemical Asset Inventory, Ergonomics, JHAs, Safety Walkthroughs, Asset Inventory, Confined Space, Fire and General Safety, Toolbox Talks, Training and Certification tracking, CAPA, Near Miss and Incident Management, Epermitting, Safety Observations, Compliance and more. We offer sophisticated dashboarding and reporting capabilities with the push of a button.
