Aerospace technical work
Define the question before building the answer.
Technical Work examines relevant needs, existing systems and evidence. Work proceeds only where a proportionate Federation contribution is justified.
Evidence & context
Reading technical evidence.
A test report, a model or an operational observation has value when the evaluated object, method and conditions are understood. These are explanatory engineering considerations—not additional AF requirements.
The setup provides context; its photograph is not a qualification result or an approval.
Illustrative engineering sceneStart with the evaluated object
Identify the article, version or operating context. A result from one configuration cannot be assumed to describe every version, integration or intended use.
Read the method and conditions
Test, analysis, inspection and demonstration answer different questions. Consider the method, equipment, configuration and conditions behind the result—not simply the report’s title.
Distinguish verification and validation
Verification considers whether specified requirements have been met. Validation considers suitability for intended use and stakeholder needs. The relevant evidence and boundaries need to be clear in either case.
Keep the conclusion within its limits
Retain assumptions, findings, uncertainty and unresolved limitations. Technical evidence supports a reasoned conclusion within those boundaries; it is not a universal performance or approval claim.
From need to maintained output
Scope disciplines the work. Review disciplines the conclusion.
Need & landscape
Describe the issue, affected users and existing references. Establish whether a meaningful gap remains.
Proposal guidanceScope & expertise
Define the audience, boundaries and output. Connect relevant competence through the appropriate technical structure.
Working GroupsEvidence & review
Develop the work, examine limitations and resolve input through reasoned technical consideration.
Consultation modelPublication & status
Authorized publication retains a defined scope and status. Review, revision or withdrawal follow as context changes.
Full technical processSelect the output by purpose
A question does not predetermine a publication.
Landscape review
Understand the existing references and whether a gap remains.
Not a new normative requirement.Framework & guidance
Organize a subject or explain context and implementation.
Explanatory, within the stated scope.Recommended practice
Describe a technically appropriate voluntary approach.
Not regulation or automatic approval.AF Standard
A controlled normative publication where a distinct need is justified.
Draft and concept status are not published requirements.Where formal requirements belong
Technical interest does not make a published standard.
AF 9100:2026
The Aerospace Quality Management System standard provides a controlled organizational and lifecycle-assurance framework. Read the First Edition and its applicability rather than inferring requirements from a web summary.
Standard and companion resourcesEight standards, distinct scopes
AF 9100–9800 cover complementary technical disciplines. Read each First Edition and its supporting resources against the actual activity and scope; access to a standard is not a conformity decision.
Explore the standards catalogueFrameworks, guidance and Recommended Practices can remain useful without becoming normative standards. The document class, version and status explain how the resource should be read.
The technical environment
Different structures contribute different kinds of continuity.
Membership is a potential contribution route, not an appointment. Following guidance does not create Recognition, Accreditation or regulatory approval.