Skip to content
Aerospace Federation

Aerospace Federation

Find your direction.

Explore the Federation. Connect with its work.
Federation sections6 areas

Choose an area to see its pages. Shortcuts are in Quick access.

Management Systems Assurance

Evaluate organisational controls and scoped supplier capability against the applicable management-system requirements. A system-level conclusion does not establish conformity of every product or competence of every technical method.

ASTRA programme familyF01AF-AST-TP-001

Scope first.
Evidence throughout.

Evaluate organisational controls and scoped supplier capability against the applicable management-system requirements. A system-level conclusion does not establish conformity of every product or competence of every technical method.

Design and production systemMaintenance systemDistribution system

Subjects within this family.

The profile retains 3 technical subjects. Inclusion here describes the framework; an individual grant covers only the specifically assessed and approved scope.

  • F01-S01Design and production system
  • F01-S02Maintenance system
  • F01-S03Distribution system

Connect the claim to actual capability.

Read the family profile with the common ASTRA standard. Application-specific criteria, local authority and real evidence must be established for the particular case.

Define the object

Identify the legal holder, actual performer, subject or configuration, site, operating conditions and requested outcome.

Demonstrate implementation

Connect applicable requirements to current personnel, methods, resources and traceable original records. Confirm that reused evidence is relevant to this scope.

Resolve the conclusion

Every applicable mandatory condition must pass, exclusions must be independently justified and in-scope nonconformities verified closed before a positive decision.

Use the conclusion actually reached.

A management-system conclusion does not approve every product, process, laboratory method or employee. It does not create maintenance authorization.

Membership, commercial relationships and a completed application do not determine the technical decision. Separate legal and competent-authority requirements continue to apply.

Programme documents.

Read the common core and this family’s profile together. These resources remain in the dedicated ASTRA collection, not the general Documents library.

First Edition / 30 September 2026. This is the publication date, not an individual approval or effective date. Technical adoption, operator authority and scope activation require their own authentic records.

Make the requested scope clear.

Describe the programme family and the actual work for initial scope review. Availability and the appropriate outcome are confirmed for the specific request; submission is not approval.