About the Federation
What We Do
How Aerospace Federation connects participation with technical, research and professional activity.
Federation functions
From participation to technical, research and professional activity.
Aerospace Federation creates routes for institutional cooperation, membership, Technical Work, Recognition, research, publications, professional development and structured exchange. Each function has a distinct purpose and should not be confused with regulatory authority.
Understand the distinction
Match the question to the function.
Different kinds of work need different evidence and different outcomes.
A shared technical question
Technical Work examines the existing landscape before deciding whether a framework, guidance, research output or a normative publication is justified.
Follow the technical processA claim about capability
A directory description, a technical contribution and a reviewed Recognition outcome are not the same claim. Check the relevant published scope and current record.
Read the review frameworkPrimary areas
Connected work with clear limits.
Structured participation
Routes through which organizations and professionals may engage responsibly and exchange relevant perspective.
Formal relationship
A structured participation framework for Corporate, Institutional and Individual members.
Voluntary technical outputs
Topic assessment, expert groups, frameworks, guidance, recommended practices and consultation where appropriate.
Separate evidence-based decision
Defined Recognition routes for eligible active members where the relevant programme is active.
Documented knowledge
Research priorities, collaborative work, reports, white papers and institutional publications.
Professional exchange
Education, development, forums, workshops, webinars and focused discussion as programmes develop.
Function matrix
What each function may produce, and what it does not replace.
| Route | Subject of Recognition | Who must hold membership | Primary evidence |
|---|---|---|---|
| Membership | Formal participation relationship | Membership status and profile | Does not create decision authority |
| Technical Work | Examine defined technical needs | Frameworks, guidance, briefs and consultation material | Does not replace mandatory standards authority |
| Recognition | Evaluate defined subjects against criteria | Recognition scope and public record | Does not replace accreditation or licensing |
| Research and publications | Develop and communicate knowledge | Research, reports and publications | Does not automatically create Technical Work |
| Academy and events | Professional learning and exchange | Learning, forums and workshops | Does not automatically create Recognition |
| Governance | Institutional oversight | Policies, decisions and review | Does not turn all participants into decision makers |
From topic to outcome
Different functions may connect without becoming the same process.
- 01Aerospace issue identified
- 02Research or technical landscape review
- 03Expert discussion
- 04Technical Work where appropriate
- 05Consultation
- 06Framework, guidance or publication
- 07Education or professional activity where useful
Recognition is separate: a technical document never creates Recognition automatically. Recognition requires separate criteria, evidence, review and decision.
Continue exploring