Establish the basis.
Governance defines responsibility. Membership connects organizations and professionals to appropriate participation routes.
GovernanceInstitutional strategy
Building the capability behind the Federation.
Participation, technical work and maintained knowledge form the basis of AF’s long-term role in aerospace. The strategy is to develop these capabilities together—not to expand programmes faster than their evidence and oversight can support.
Read the development roadmapConnected priorities
An institution built through mutually supporting functions.
AF’s early development depends on the quality of participation, technical process and public information. A new programme is useful only when there is a defined need and the capability to support it.
Development architectureThree functions · one institutional basis
Develop useful outputs.
Committees, review and the Standards Programme turn justified questions into scoped standards, guidance and technical knowledge.
Technical WorkSupport practical exchange.
Participation and supplier discovery should connect capabilities, without treating visibility as competence or approval.
SKYLINK overviewA membership base that contributes.
Membership development is not simply a question of numbers. The priority is an active professional network: institutions and individuals bringing operational context, technical experience and research perspectives into relevant work. Participation should build representation and long-term capacity, not imply automatic appointment or authority.
Structures that give expertise continuity.
Councils connect broad sector perspectives and frame priorities. Technical Committees coordinate defined fields; Expert Working Groups address bounded tasks. As activity develops, these structures can review proposals, support standards, guidance and research, and connect findings to the appropriate AF process.
Technical capability
Standards need a technical basis—and a maintained life.
The long-term intention is a structured portfolio of voluntary aerospace standards and technical documents, developed for practical relevance across international aerospace contexts.
Published foundation
AF 9100:2026
Aerospace Quality Management System
First Edition · PublishedThe quality and lifecycle-assurance foundation within the AF 9100–9800 standards collection.
Publication & companion resourcesExpand through need, review and maintenance.
Technical Work first examines existing regulation, standards, research and practice. A new normative publication is justified only where a defined need remains; another output—or no new document—may be more appropriate.
- Define the need
- Draft & review
- Seek relevant input
- Publish & maintain
Transparent scope, competent contributors, stakeholder participation and controlled revisions should support the portfolio as it develops. AF 9100–9800 are available with their First Editions and dedicated supporting document collections.
AF Standards are voluntary technical publications unless adopted by a specific contract, programme or authorized arrangement. Applicable law and competent-authority requirements remain independently applicable.
Digital projects
Infrastructure in service of the institutional model.
Digital projects should connect member systems, standards access, Recognition records and knowledge resources. These projects address different needs within that wider model; they are not its entirety.
Digital project portfolioConnect · Apply · Advance
AF SKYLINK
Discover suppliers, capabilities and sourcing connections.
Sourcing & supplier networkSupplier-provided information ≠ independently reviewed evidence.
AF POLARIS
Translate requirements into practice with guidance, templates and references.
Practice & implementationImplementation support ≠ additional or replacement requirements.
AF ZENITH
Understand maturity, identify improvement priorities and reassess progress.
Maturity & improvementSelf-assessment and maturity ≠ certification.
Three systems. Distinct purposes.
The portfolio relationship is CONNECT → APPLY → ADVANCE: supplier discovery, practical implementation and organizational improvement. Each project has its own scope and information boundaries.
Recognition & assurance
Different functions. Different conclusions.
Credibility depends on keeping participation, requirements, evidence review and information disclosure distinct.
Recognition should mature through transparent criteria, documented review, conflict management, independent decisions and appropriate maintenance. Membership remains an entry condition where required—not the evidence for the outcome.
Information boundariesRead each conclusion within its scope
ParticipationMembership A relationship—not technical approval
Separate evidence review
AcknowledgementRecognition Eligible active members · defined scopeParticipation alone does not establish the evidence for Recognition.
- Standards
- Controlled requirements
Publication is not a conformity decision. - Accreditation
- Assessed competence
Defined conformity-assessment or specialist activities. - Certification information
- A separate conformity claim
Verify issuer, scope and status. - Supplier declarations
- Supplier-provided information
Not automatically independently verified.
Research & technical knowledge
Knowledge should inform decisions, not simply fill a library.
The strategic direction is to develop useful technical reports, industry studies, research publications, articles, sector insights, Committee outputs and future-trend analysis. Their value lies in traceable evidence and stated limitations—not publication volume.
Research can identify a need; Committee work can frame it; publication can share findings. Neither a research result nor a published perspective automatically becomes a standard requirement.
Institutional roadmap
Progress through readiness, not arbitrary deadlines.
These phases describe a direction, not a dated schedule or a claim that a phase is complete. Activities may overlap; progression depends on resources, competence, evidence and governance readiness.
Intended development routeReadiness gates, not completion markers
-
Near-term emphasis
Foundation
Establish the institutional basis.
- Clarify governance mandates and decision routes.
- Build membership and expert participation.
- Define technical priorities and the initial standards framework.
Readiness to build onClear responsibilities, bounded work items and reviewable records.
-
Next-stage emphasis
Development
Build repeatable technical capability.
- Develop Council, Committee and Working Group activity.
- Extend reviewed standards, guidance and publications.
- Strengthen Recognition criteria, review and maintenance.
Readiness to build onCompetent participation and consistent technical processes.
-
Medium-term direction
Integration
Connect resources and services.
- Link standards with implementation material.
- Connect digital resources through reviewed interfaces and clear information boundaries.
- Connect member input, knowledge and improvement feedback.
Readiness to build onClear data boundaries, usable resources and accountable delivery.
-
Long-term direction
Maturity
Maintain a durable international institution.
- Revise programmes and expand technical coverage.
- Strengthen oversight and international engagement.
- Develop sustained research and industry insight.
Readiness to build onMaintained outputs, institutional continuity and useful participation.
Strategy in action
A continuous route from participation to learning.
The intended cycle connects institutional functions. It is not an automatic approval chain: each programme retains its own scope, review and decision requirements.
Institutional learningUse → review → revise
Technical development
Evidence, Working Groups and review shape appropriate outputs.
Technical Work ProcessPractical use
Organizations apply relevant resources within their own responsibilities.
POLARIS overviewReview & feedback
Separate review processes and structured assessment perspectives can reveal gaps and learning.
Criteria & Review
Feedback from use, review and research returns to priority setting and future revisions.
Measuring progress
Evaluate capability through evidence.
Progress should be assessed through quality and consistency of activity, not unsupported growth claims or numerical targets.
Participation & governanceIs participation supported by accountable structures?
Examine relevant member engagement, functioning mandates, responsible Committee activity and traceable decisions.
Technical output & maintenanceCan technical work be reviewed and maintained?
Examine defined work items, competent review, useful publications and controlled standards development and revision.
Recognition & process integrityDo conclusions remain evidence-based and bounded?
Examine clear criteria, documented evidence, managed conflicts, bounded records and appropriate ongoing review.
Digital & knowledge readinessAre resources ready to support their intended use?
Examine reviewed project development, usable resources, publication activity and consistent information boundaries.
This strategy is a development reference. Programme pages and controlled publication records remain the sources for current scope, status and availability.
Contribute a technical need