MRO organizations do not always need AS9100. AS9110 is usually more suitable when your core business is aircraft or component maintenance, repair, and overhaul rather than design and new production. However, what you actually need is driven by customer contracts, regulatory expectations, and how your organization is scoped.
How AS9100 and AS9110 differ for MRO
At a high level:
- AS9100 extends ISO 9001 for aerospace design and manufacturing organizations.
- AS9110 extends ISO 9001 for aerospace maintenance organizations (MRO), including line, base, and component maintenance.
AS9110 emphasizes topics that are critical in MRO environments, such as maintenance process control, configuration control of in-service assets, verification after maintenance, and release to service. AS9100 emphasizes design control and new production processes, which may be less central to a pure MRO facility.
When AS9110 is usually more suitable
AS9110 is often a better fit if:
- Your organization does not design or manufacture new aerospace products, and instead focuses on inspection, overhaul, modification, and repair.
- You operate primarily as a maintenance organization under aviation authorities (for example, EASA Part-145, FAA repair station), and your customers expect an MRO-focused aerospace quality standard.
- Your processes center on workscoping, disassembly, inspection, repair/overhaul, reassembly, test, and release to service of aircraft and components.
- You need a standard that directly addresses used parts, maintenance records, configuration control of in-service assets, and control of outsourced repairs.
In those cases, AS9110 typically reflects reality in an MRO shop more directly than AS9100. It can make your quality system, documentation, and audits better aligned with day-to-day maintenance workflows instead of design and new build flows.
When AS9100 may still be required or beneficial
There are scenarios where AS9100 is required, or where organizations choose to maintain AS9100 in addition to, or instead of, AS9110:
- Mixed operations: If your site both manufactures new components and performs MRO activities, some OEMs and primes may prefer AS9100 for the whole site to keep supplier qualifications simpler.
- Design activity present: If you hold design authority (for example, repairs, modifications, STCs, DER/DOA/ODA work) or perform significant design and development, customers may insist on AS9100 or a combination of AS9100 and AS9110.
- Customer mandates: Some OEMs and defense customers specify AS9100 in supplier qualification requirements and may not yet fully recognize AS9110 as equivalent for their risk model. In those cases, your choice is constrained by contract.
- Corporate standardization: Large multi-site organizations sometimes adopt a single corporate standard (often AS9100) for consistency even if parts of the operation are primarily MRO.
If you are in any of these categories, you should expect to map your actual processes carefully against the required standard and be explicit about scope in your quality manual. You may also need to justify to customers and auditors how MRO-specific risks are addressed if you rely only on AS9100.
Scope definition and brownfield reality
The decision is rarely a clean switch between standards, especially in brownfield environments that already have a certified system, legacy documentation, and integrated MES/ERP/QMS stacks.
- Scope matters more than the label: Certification bodies certify a scope and site, not just an industry code. You can scope one site or unit as AS9110 and another as AS9100, as long as interfaces, hand-offs, and responsibilities are clearly defined and documented.
- Mixed systems and lifecycles: If you are running older ERP/MES/QMS tools configured around AS9100, moving to AS9110 is not just changing the certificate. It impacts procedures, routing logic, work instructions, records, and approval flows. In regulated environments with long equipment and data lifecycles, this can be a multi-year change under strict change control.
- Validation and qualification burden: Any significant QMS restructuring in a safety-critical or defense context affects training, validation, and often customer approvals. Full replacement of systems or standards at once is high risk and often fails due to downtime constraints, integration debt, and the cost of requalification.
Many organizations therefore evolve incrementally: maintaining AS9100 where required, while introducing AS9110-aligned practices in MRO units and harmonizing procedures gradually.
What actually drives the decision
From a practical standpoint, your choice should be driven by a set of concrete factors rather than a generic preference:
- Contractual requirements: What do your current and target customers specify: AS9100, AS9110, or both? Are there flow-down requirements from OEMs or defense agencies?
- Regulatory environment: How does your QMS intersect with aviation authority approvals (for example, Part-145, Part-21, military equivalents)? Some authorities are familiar with both standards; others may have a de facto expectation.
- Operational profile: What percentage of your work is new build vs. MRO vs. modification/design? Where is the higher risk and scrutiny?
- Existing QMS and IT systems: Is your current QMS structure, electronic records, and system validation more aligned to production or maintenance? What is the realistic cost and risk of re-alignment?
- Supplier and site structure: Do you have multiple sites with different functions, and can you scope certifications differently without breaking traceability or overcomplicating audits?
In many cases, a pure MRO business without design or manufacturing responsibilities is well served, and often better served, by AS9110 if customers accept it. A hybrid organization may need AS9100, or a combination, to cover the full lifecycle from design and production through sustainment.
Implications for digital systems and traceability
Whether you align to AS9100 or AS9110, regulators and customers will expect robust traceability, controlled documentation, and auditable records across maintenance and modification activities.
- Traceability and configuration control: MRO environments must show which parts were removed, replaced, or repaired, with full lineage, especially for life-limited and serialized items. Your systems (ERP, MES/MRO, QMS) need to support this regardless of the chosen standard.
- Change control and long lifecycles: Procedures, digital travelers, and work instructions evolve slowly in heavily regulated MRO contexts because each change impacts training, approvals, and often external audits. Any shift between AS9100 and AS9110 needs a phased, controlled plan.
- System coexistence: It is common to have separate but integrated solutions for production, engineering, and MRO. The standard you certify to does not replace the need to map interfaces carefully: how nonconformances, concessions, and maintenance data cross between systems.
The standard should be one part of a coherent architecture for quality and traceability, not a stand-alone decision.
Bottom line
MRO organizations do not always need AS9100. AS9110 is often more appropriate for pure maintenance organizations, but customer and regulatory requirements, mixed operations, and existing systems often constrain the choice. The safest approach is to analyze your actual operations and contracts, define a clear scope, and then select or combine standards accordingly, recognizing the change-control and integration implications of any shift.
