FAQ

When should an organization adopt AS9110 or AS9120 instead of AS9100?

AS9110 and AS9120 are sector-specific aerospace quality management standards that build on ISO 9001, similar to AS9100 but for different roles in the value chain. You typically choose AS9110 or AS9120 instead of AS9100 when your organization is primarily a maintenance organization (AS9110) or a stockist/distributor (AS9120), and you do not perform aerospace design and production activities covered by AS9100.

When AS9100 is usually the right fit

AS9100 is generally appropriate when you:

  • Design aerospace products (airframes, engines, avionics, systems, components).
  • Manufacture or assemble parts, structures, or systems for OEMs, primes, or Tier 1–3 suppliers.
  • Control production processes (machining, fabrication, special processes, integration, testing).
  • Have responsibilities for product realization that go beyond distribution or maintenance.

In regulated and defense contexts, primes frequently specify AS9100 for design and production suppliers. If you are cutting metal, molding composites, doing special processes, integrating systems, or holding design authority, AS9100 is usually the baseline expectation.

When AS9110 is a better fit

AS9110 focuses on aerospace maintenance organizations, including MRO providers for aircraft, engines, components, and line maintenance. It is more suitable than AS9100 when you:

  • Provide maintenance, repair, and overhaul services on in-service aircraft, engines, or components.
  • Operate in environments governed by continuing airworthiness, OEM maintenance manuals, and regulatory approvals (for example, under civil aviation authorities or defense equivalents).
  • Do not design new products or run serial production of new hardware, but instead service existing configurations and part numbers.
  • Manage return-to-service decisions, maintenance records, service bulletins, AD compliance, and configuration status of in-service assets.

AS9110 includes controls specific to MRO risk profiles, such as release to service, maintenance documentation control, human factors in maintenance, and configuration management of in-service equipment. If your primary value is maintaining airworthiness of existing assets rather than producing new ones, AS9110 is usually more aligned with your operations.

When AS9120 is a better fit

AS9120 targets organizations that buy, store, and distribute aerospace parts but do not perform transformation processes on those parts. It is generally a better choice than AS9100 when you:

  • Act as a stockist/distributor or broker of aerospace hardware or materials.
  • Do not perform design, significant manufacturing, or overhaul work on the products.
  • Focus on traceability, storage, preservation, and release of approved parts and materials.
  • Rely heavily on upstream OEMs and approved sources for conformity and documentation.

AS9120 emphasizes controls around counterfeit risk, product traceability, shelf-life management, storage conditions, and documentation flow through the supply chain. If your risk profile is about ensuring the right certified part reaches the right customer with correct documentation and no degradation or counterfeit risk, AS9120 is typically more appropriate.

Organizations that may need more than one standard

Many aerospace businesses, especially in brownfield environments, operate multiple business models under one roof. You may need to consider more than one standard when you:

  • Design and manufacture parts (AS9100) and also perform MRO activities on similar equipment (AS9110).
  • Manufacture parts (AS9100) and also operate a distribution business unit selling third-party parts (AS9120).
  • Provide integrated services such as engineering, production, spares distribution, and in-service support.

In these cases, some organizations:

  • Maintain one integrated QMS and scope statement that references multiple standards, with clear boundaries by site, process, or business unit.
  • Run separate certifications for different legal entities or operating locations.

This quickly interacts with traceability, IT, and MES/ERP/QMS integration. Mixing MRO, distribution, and production workflows in the same systems often exposes gaps in routing, revision control, and record retention if the QMS scope and digital workflows are not clearly separated and validated.

How to determine which standard is appropriate

The choice is driven less by preference and more by your actual activities, risks, and customer/regulatory expectations. Practical steps:

  1. Map your value streams
    List each major value stream: design & development, new production, MRO, distribution/stockist activities, and any combination of these.
  2. Align activities to standard intent
    For each value stream, decide whether its primary risks and responsibilities align more with AS9100, AS9110, or AS9120.
  3. Review customer and contract requirements
    Many primes and regulators specify which standard is expected for which activity. In some cases, AS9100 is required even where AS9110 or AS9120 could technically fit.
  4. Consider your long-term strategy
    If you plan to add design or manufacturing capabilities, AS9100 may be the more future-proof base, with AS9110/AS9120 added later as appropriate.
  5. Evaluate integration and validation impact
    Introducing or expanding standards in a brownfield stack (MES, ERP, PLM, QMS) affects procedures, records, and evidence trails. Plan for validation, change control, and limited downtime windows.

Tradeoffs and constraints

Key tradeoffs to acknowledge:

  • Complexity vs. specificity: Adopting AS9100 for everyone can simplify the story but may add controls that are not well-matched to MRO or distribution activities. Using AS9110 or AS9120 where appropriate provides better alignment but increases certification complexity if multiple standards are in play.
  • Certification scope management: In mixed operations, defining which locations, processes, and systems fall under which standard is non-trivial. Poor scoping leads to audit findings and operational confusion.
  • IT and system coexistence: Legacy ERP, MES, and QMS platforms are often not structured to distinguish clearly between production, MRO, and distribution flows. Trying to implement multiple standards without rethinking routing, status control, and record structures can create traceability gaps.
  • Long equipment and system lifecycles: Plants and MRO shops often run equipment and software for decades. Replacing or heavily modifying systems purely to align with a standard is rarely feasible due to validation cost, downtime risk, and integration debt.

In practice, many organizations layer the chosen standard(s) onto existing systems through procedures, work instructions, and incremental configuration changes rather than full platform replacement.

Why not just upgrade everything to AS9100?

Some organizations consider making all operations AS9100-certified to simplify messaging. This can work, but there are limitations:

  • AS9100 is optimized for design and production; it may not address some MRO-specific or distribution-specific risks covered more explicitly in AS9110/AS9120.
  • Regulators, airworthiness authorities, or primes may explicitly ask for AS9110 for MROs or AS9120 for distributors.
  • Maintaining AS9100 controls where they are not value-adding can increase bureaucracy without improving risk control.

In heavily regulated or defense environments, certification strategy should follow the actual risk profile and regulatory expectations of each line of business, not just brand considerations.

Connecting to digital systems and brownfield environments

Whatever standard you choose, auditors will look for consistent evidence in your digital and paper records. For example:

  • AS9100: design records, production travelers, inspection data, FAI records, nonconformance and CAPA workflows.
  • AS9110: maintenance work cards, configuration status of individual assets, return-to-service records, and line maintenance traceability.
  • AS9120: lot/batch traceability, storage conditions, shelf-life tracking, release documentation, and supplier documentation control.

In brownfield shops with multiple legacy systems, you rarely replace everything to “be compliant”. Instead, you typically:

  • Clarify which processes and systems support each certified scope.
  • Strengthen document control, revision control, and data integrity practices around existing tools.
  • Use incremental digitization (for example, digital travelers, improved QMS workflows) where gaps threaten traceability or auditability.

This approach respects constrained downtime, avoids unnecessary requalification of equipment and software, and better fits long lifecycle aerospace environments.

Get Started

Built for Speed, Trusted by Experts

Whether you're managing 1 site or 100, C-981 adapts to your environment and scales with your needs—without the complexity of traditional systems.