How often does AS9100 typically get revised?

AS9100 does not follow a fixed, predictable revision schedule. Historically, major revisions have been driven by updates to ISO 9001 plus additional aerospace-sector needs.

Historical revision pattern

Looking at past versions gives a rough sense of cadence:

• AS9100 (original): 1999
• AS9100A: 2001
• AS9100B: 2004
• AS9100C: 2009
• AS9100D: 2016

From this history you can infer:

• Early on, revisions were relatively close together as the standard matured.
• More recently, major revisions have been on the order of 7–10 years apart, aligned with ISO 9001:2008 and ISO 9001:2015 changes.

No guaranteed timetable

There is no official, fixed interval (for example, “every 5 years”) for AS9100 revisions. Timing depends on:

• Revisions to ISO 9001, which AS9100 builds on.
• IAQG decisions about sector-specific needs, risks, and lessons learned.
• Feedback from certification bodies, OEMs, and regulators.

Because of this, you cannot reliably plan capital projects or system overhauls around a predicted next revision date. In regulated, long-lifecycle environments, most organizations instead treat AS9100 as a slowly evolving baseline and adjust incrementally as new guidance or customer requirements appear.

What changes between major revisions

Major revisions (like AS9100C to D) typically introduce:

• New or restructured clauses to maintain alignment with ISO 9001.
• Updated expectations around risk, special processes, and configuration management.
• Clarifications around product safety, counterfeit parts, and external provider control.

In brownfield environments with established QMS, MES, and ERP systems, these changes usually translate into:

• Revisions to documented processes and procedures under formal change control.
• Updates to digital forms, workflows, and records (e.g., NCR, CAPA, FAI, audit checklists).
• Targeted training and competence updates for key roles.

Full system replacement purely to “chase” a new AS9100 revision is rare and often impractical because of validation burden, integration complexity, and downtime risk. Most organizations adapt existing systems through configuration and supplemental controls.

Between revisions: what actually moves

Even when the core AS9100 standard is stable for years, requirements still evolve through:

• Sector-specific guidance and clarifications from IAQG and certification bodies.
• OEM and prime contractor flow-downs that tighten expectations beyond baseline AS9100.
• Customer-specific audit findings that drive new or more detailed controls.

Operationally, this means you should treat AS9100 as a minimum, and expect to maintain:

• Ongoing document control and revision management for procedures and work instructions.
• Traceable updates to digital systems, forms, and data models under change control.
• Evidence that changes have been trained, implemented, and are effective.

Planning implications for aerospace manufacturers

For operations, engineering, quality, and IT leaders, the practical approach is:

• Monitor IAQG, certification body, and OEM communications rather than assuming a fixed update cycle.
• Design QMS and supporting systems to absorb requirement changes through configuration (fields, workflows, reports) rather than large-scale replacement.
• Maintain clean traceability from AS9100 clauses to your internal procedures, forms, and records so impact assessment is efficient when a revision does occur.
• Budget for periodic QMS refresh projects (process, training, and system configuration) roughly in line with the historical 7–10 year major revision pattern, recognizing timing may shift.

In short, AS9100 is typically revised on a multi-year cycle tied to ISO 9001 updates, but the exact timing is uncertain. For most aerospace and defense manufacturers, resilience comes from robust document control, change management, and flexible systems rather than trying to predict the exact year of the next revision.