Yes, a small aerospace supplier can realistically meet AS9100 requirements, but it requires deliberate scope, disciplined documentation, and leadership commitment. AS9100 does not mandate company size or specific software; it mandates a risk-based quality management system (QMS) that you can demonstrate, control, and maintain.
What AS9100 actually expects from a small supplier
AS9100 is an extension of ISO 9001 with added aerospace, defense, and aviation requirements. For a small shop, the core expectations are:
- A defined, documented QMS that covers the work you perform (design, manufacturing, special processes, inspection, etc.).
- Clear responsibilities and authorities, even if a few people hold multiple roles.
- Documented, controlled processes for quoting, review of requirements, planning, production, inspection, release, and handling nonconformances.
- Risk-based thinking around critical parts, special processes, and changes.
- Configuration management and traceability appropriate to the products you make.
- Evidence: records that show you follow your processes consistently.
None of this requires being a large organization, but it does require structure and repeatability that many small suppliers do not have initially.
Where small suppliers typically struggle
Common pain points for smaller organizations include:
- Documentation vs. capacity: One person is often the quality manager, document control, and internal auditor. If that person is overloaded or leaves, the system quickly erodes.
- Informal processes: Tribal knowledge and verbal instructions conflict with the need for controlled procedures, work instructions, and records.
- Configuration and revision control: Managing drawing revisions, router changes, and customer specifications across email, network folders, and ERP can be fragile.
- Internal audits and management review: These are often late, rushed, or treated as a one-time pre-audit activity instead of an ongoing process.
- Nonconformance and corrective action: NCRs might be logged, but root cause, corrective actions, and effectiveness checks are often weak or undocumented.
- Training records: People are competent, but proof is scattered in spreadsheets, emails, or not documented at all.
These gaps do not mean AS9100 is unrealistic. They mean you must right-size how you address them and be honest about resource limits.
Right-sizing AS9100 for a small organization
AS9100 allows scalability, but you have to justify how you scale. Practical approaches for small suppliers include:
- Scope the QMS carefully: Limit the scope to the products and services you actually provide. Do not declare design responsibility if you only build to print.
- Keep procedures lean: A 2–3 page clear procedure that people follow is better than a 30-page template no one reads. Focus on clarity and control, not volume.
- Combine roles explicitly: It is acceptable for one person to be quality manager, document control, and internal auditor, as long as conflicts of interest are managed and competence is demonstrated.
- Use existing tools: You can run an AS9100 system with paper, spreadsheets, and a basic ERP if you have good control and revision discipline. Dedicated software can help, but it is not a prerequisite.
- Target high-risk areas first: Prioritize configuration management, special processes, FAI/AS9102, and nonconformance management, because these are high-impact in audits and operations.
Coexisting with your current systems and tools
In a brownfield environment, you will usually be layering AS9100 discipline over existing ERP, shared drives, and manual workflows, not replacing them:
- ERP and job travelers: Use your current travelers or routers, but control the templates, revision, and linkage to the latest drawings and specs.
- File shares and email: If drawings are on a shared drive, define naming, folder structure, and who can change what. Uncontrolled email attachments create traceability risk.
- Paper records: Paper is acceptable if you can find it, it is legible, and there is a retention system. The audit risk is loss, misfiling, and version confusion.
- Incremental digitization: Introducing digital travelers, electronic FAI, or NCR workflows can reduce risk, but each change must be planned, validated, and documented under change control.
Full replacement of ERP/MES/QMS tools is rarely necessary or wise for a small supplier. The validation burden, migration risk, downtime impact, and cost often exceed the benefit unless the current systems are failing outright.
Evidence and audit readiness
For a small supplier, the main audit risk is not the absence of a fancy system, but the inability to show consistent evidence. You should be able to:
- Pull a job at random and show the contract review, traveler, inspection records, special process certs, and final release decisions.
- Trace a critical characteristic from drawing to inspection plan to recorded result.
- Show how you handle a nonconformance from detection to disposition to corrective action.
- Demonstrate control of external providers, including purchase order requirements, supplier performance data, and flowdown of customer and regulatory requirements.
- Produce recent internal audit reports, management reviews, and actions taken.
Auditors expect imperfection, especially in smaller organizations. What they do not accept is a mismatch between what your procedures say and what you actually do, or the inability to find records.
Resourcing and sustainability considerations
Even if initial certification is achievable, sustaining AS9100 is often the harder problem for small suppliers:
- Single-point-of-failure risk: If one quality manager holds all knowledge, a departure or illness can destabilize the system.
- Busy-period shortcuts: When production spikes, internal audits, training, and CAPA follow-up often slip first, creating findings at surveillance audits.
- Change control drift: Uncontrolled process changes, tooling updates, or drawing interpretation shortcuts can erode compliance over time.
Plan for at least minimal redundancy in QMS knowledge, distribute responsibilities, and schedule system activities (audits, reviews, calibration, training) as non-optional work, not “if we have time” tasks.
Tradeoffs to be explicit about
Before committing, leadership should recognize key tradeoffs:
- Cost vs. opportunity: AS9100 brings access to more aerospace work and preferred supplier status for some customers, but there are ongoing costs in audits, maintenance, and lost flexibility.
- Formality vs. speed: Increased formality slows ad-hoc changes and improvisation. This protects quality and traceability, but may feel restrictive to small, hands-on teams.
- Incremental improvement vs. big-bang redesign: Trying to replace all systems at once to “get ready” for AS9100 usually fails in small, brownfield shops. Incremental tightening and digitization, with validation, is more realistic.
Bottom line
Yes, a small aerospace supplier can realistically meet AS9100 requirements. Success hinges less on size and more on:
- Leadership willingness to accept the ongoing workload and discipline.
- Honest scoping of the QMS to what you actually do.
- Right-sized, documented processes that people follow.
- Robust evidence trails that align with those processes.
- Careful coexistence with existing ERP, paper, and manual systems instead of risky full replacement.
Certification is attainable, but it is a strategic commitment to how you operate, not just a checklist to pass a one-time audit.
