Aerospace Federation
Choose an area to see its pages. Shortcuts are in Quick access.
Useful destinations
Try another term, or search the site's full content.
Integrated technical & lifecycle assurance
Aerospace Standard
A defined scope. Traceable evidence. An independent conclusion.
One framework for technical and lifecycle assurance across aviation, space, defense and future systems.
An integrated framework
ASTRA connects programme governance with technical assurance. It evaluates a named object and its real conditions—not an unlimited claim of aerospace competence.
Define the legal entity, actual performer, site, configuration, lifecycle role and intended outcome first. Then assemble the applicable common controls, family requirements, technical provisions and normative annexes.
Programme families / F01–F08
The families organise technical scope; they are not eight interchangeable certificate types. Every real scope needs its own approved profile and activation.
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.
Connect the actual product or process configuration to design, qualification, manufacturing and release evidence. Critical activities require application-specific criteria and demonstrated technical coverage.
Define competence by method, range, site and operating conditions. Traceability, uncertainty, method validation and witnessed performance support valid technical results—not an equipment list alone.
Examine named programmes, disciplines, levels and delivery routes through direct evidence of learning, moderation and learner protection. Programme recognition is separate from professional licensing or individual task authority.
Evaluate defined aerodrome capability, local operating interfaces and accountable delivery. Heliports, vertiports and spaceport interfaces need their own applicable criteria; a generic airport profile does not grant wider operating permission.
Follow facility, aircraft type and task capability through current technical data, parts history, human factors, task execution and handover. A maintenance scope does not automatically cover every internal test or training activity.
Distinguish headquarters arrangements from the real station, service and provider carrying out the work. Evaluate handovers, local variations and disrupted operations; airline flight operations are not included by default.
Keep environmental capability, historical statement verification and prospective plan validation distinct. Each claim needs its own boundary, period, method and assurance form; a validated forecast is not an achieved reduction.
Technical basis: core Clauses 17–24 and Annex S; family profiles AF-AST-TP-001–008. Listing a subject does not establish a live service or operating permission.
Lifecycle & technical depth
Research, design, manufacture, integration, test, operation, maintenance, modification and retirement create different evidence needs. Configuration, environment and retained responsibility must remain visible across those handovers.
Reading route: Clauses 32–80; Annex AK (all-space domains), Annex AO (parameter schedules), Annex AM (synthetic calculations) and Annex AN (decision diagrams). The visual sequence is explanatory, not a new normative process.
Independent decisions
Evidence validity is established before a result is classified. Every state needs a reason and traceable support; unresolved evidence cannot be treated as success.
The approved condition is met by valid evidence.
Valid evidence shows that the condition is not met.
Applicability, method, evidence, uncertainty or authority remains unresolved.
The trigger and retained responsibility are absent; exclusion is independently approved.
In-scope nonconformities must be verified closed, exclusions justified, and decision authority competent and independent. A weighted score, completed form, fee or membership cannot compensate for an unmet requirement.
Accreditation evaluates a conformity-assessment body’s scoped competence. Recognition, qualification and certification concern their own defined objects and criteria. Verification addresses historical statements; validation examines prospective claims.
The First Edition date identifies the documents. Technical approval, institutional adoption, operator appointment and individual scope release require separate authentic records. This page is not an announcement that every ASTRA service is open.
A practical reading route
Read the common standard, then select the guide and profile that match the work. Supporting documents do not silently amend the core requirements.
Understand the requested outcome and prepare a scoped dossier.
PDF, opens in a new tab02 / Reading routeEstablish competent, impartial assignments and evidence coverage.
PDF, opens in a new tab03 / Reading routeBuild application-specific requirements and acceptance criteria.
PDF, opens in a new tab04 / Reading routeConnect authority, assessment, decisions and continuing controls.
PDF, opens in a new tabDedicated ASTRA collection
108 controlled document codes in ten groups. First Edition · 30 September 2026 · English. These PDFs are available here, separately from the general Documents library.
Read standard PDF in a new tabControlling technical basis
ASTRA — Aerospace Standard
108 documents in the collection
View online or download the original PDFDependency-led development and implementation of the retained 108-document ASTRA portfolio against the supplied 248-page FIRST EDITION. Eight families and 68 technical subjects remain unchanged; space and verification tags extend technical applicability without new family codes.
Code-preserving inventory and source-to-document navigation for the expanded 108-PDF ASTRA collection. The supplied 248-page core is retained unchanged; the other 107 documents are developed against its Clauses 0–80 and applicable annexes.
Integrated aerospace and all-space technical, lifecycle and independent assurance, within the actual evaluated scope.
Provide access based on published eligibility and actual scope capability while keeping membership, commercial relationships and independent conformity decisions separate. Every enquiry, applicant, participant, holder and programme service interface across F01-F08, including small organisations, individuals acting within a defined role, and multi-site or multinational applicants.
Support reproducible decisions from relevant, verifiable and configuration-specific evidence without allowing scores, reputation or document presence to compensate for missing essential conditions. All technical evaluation, evidence acceptance, method selection, source reuse, measurement decisions, specialist advice and independent outcomes within the ASTRA programme.
Make environmental claims transparent, technically supportable and distinct from operational permission, engineering suitability and accreditation of the verifier. All environmental capability, historical inventory or reduction verification, prospective plan validation, resource and climate claims, supply attributes and public environmental wording across the eight families.
Enable responsible innovation through bounded use, explicit evidence gaps, credible validation and attributable human decisions rather than technology labels or automated approval. Software, AI, autonomy, digital twins, digital evidence, defensive cyber assurance, remote operations and materially novel technologies affecting ASTRA products, processes, services or decisions.
The full programme lifecycle, from authority and profile development through enquiries, assessment, independent decisions, surveillance, remedies and responsible closure. Applies to the scheme operator and its assigned functions; it is not imposed in full on every individual applicant.
Accrediting-operator and technical-provider work for testing, calibration, inspection, system/product/process/service/personnel certification, verification/validation, proficiency activities and reference-material production. Each provider activity retains its own profile and demonstrated methods.
Educational programmes, aerodromes, maintenance facilities, technical support and station/service capabilities, with environmental statements evaluated through their separate engagement. Designed for coordinated but independently bounded F04-F08 assessment.
Admission of an evaluation dossier to independent review, gate testing, accreditation panels, other outcome decisions, urgent protective actions, notices, appeals and historical corrections.
Administration of source records, evidence-purpose states, relationships, event chronology, decision-linked credentials, public status, access, local tool validation, migration, recovery and custody.
Choosing an available outcome, preparing evidence and participating in the complete assessment and continuing cycle.
Accepting a competent, impartial assignment; planning scope coverage; observing actual work; evaluating uncertainty and counter-evidence; reporting without prejudging the independent decision.
Turning a retained scope subject into an evaluable application-specific profile, with prospective criteria, representative methods, decisions, continuation and release conditions.
Testing real implementation and closing gaps before independent evaluation without turning self-assessment into accreditation or an unsupported completion score.
Method/range/site scope, responsible technical roles, measurement suitability, method validation, witness trails, nonconforming work and bounded reporting.
Named programmes, disciplines, levels, delivery routes, direct learning evidence, moderation, completion and teach-out.
Conventional aerodromes, heliports, vertiports, spaceport interfaces and shared civil/military sites with local evidence and separate permissions.
Facility/type/task capability, current data, parts and life history, human factors, task execution, release and customer handover.
Headquarters and local implementation of G01-G09, actual providers, handovers, disrupted services, digital integrity and separate authority.
Environmental capability, historical verification, prospective validation, boundaries, factors, comparable reduction, resource flows and exclusive attributes.
Purpose-specific credibility, configuration and data lineage, adverse cases, accountable human authority, safe pilots, validated changes and semantic recovery.
Source-linked answers to practical questions about all eight families and the expanded technical and lifecycle provisions.
All controlled ASTRA publications and case records, including paper records, signed PDFs, local databases, shared records and public projections. Working copies and source records must remain distinguishable.
Normative development and profile release across F01-F08, including the added technical subjects in core Clauses 32-80. An application-specific value and a programme-wide rule have different approval boundaries.
Admission to organisational, process/product, provider, educational, operational and environmental work. Development enquiries are handled separately from applications for already released technical scopes.
All case tuples, activity-based applicability, local/remote interfaces and reliance on prior results. This procedure controls the meaning of the claim before planning time or issuing a certificate.
Application reviewers, auditors, leads, technical specialists, reviewers, decision makers and appeal functions. Applicant employer task authority is also checked where it supports a capability claim.
Institutional and personal threats to impartiality, including ownership, funds, employment, consultancy, family, close personal and adversarial relationships.
Planning by object, sites, methods, shifts, actual performers, conditions and consequence. Organisational AF 9100 time rules are not transplanted into laboratory witnesses or personnel examinations.
Live video, remote instruments, secure document rooms, telemetry, prerecorded material and controlled simulation. Suitability is determined per task, not for a whole organisation by default.
Witnessing of manufacturing, testing, inspection, maintenance, services, education or statement activities within an approved profile and safe access boundary.
Measurands, references, corrections, uncertainty and decision rules used in every relevant family. Measurement confidence, detection performance and administrative completion percentages are not interchangeable.
Internal checks, independent comparisons, proficiency activity and technically justified alternatives for significant testing, calibration, inspection or statement fields.
Laboratory, inspection, assessment, educational, operational and environmental reports, with the distinctions required by their actual result class.
All technical and administrative findings, with separate immediate protection, corrective action, independent status decisions and historical-output review.
All independent programme outcomes; accreditation panels and other outcome authorities retain their distinct rules. This process cannot supply absent technical evidence by voting.
Continuing capability and conformity status across the actual granted scope. Historical instance statements retain their object and period rather than an invented two-year technical validity.
Independent restriction, suspension, restoration and withdrawal of an exact ongoing scope, with technical containment and historical instance corrections handled separately.
Accessible programme remedies, independent appeals, fair investigation and systemic correction. This route does not replace statutory remedies or create a universal legal jurisdiction.
Protected reporting and investigation interfaces across staff, applicants, suppliers, learners and third parties, with fair response and proportionate confidentiality.
Protected case dossiers, examination content, operational/security evidence, public registry views and transfers between providers or systems.
Defensive incident handling for engineering, production, assessment and public-status systems. No intrusive security testing is authorised by this procedure.
Certificates, scope schedules, registry records, public verification, authorised artwork and claim correction. Administrative publication does not create the underlying technical decision.
Provider competence, written authorisation, binding cooperation arrangements, subcontracting and retained issuer responsibility. Ordinary applicants remain separate from delegated operators.
Outcome-neutral financing, transparent terms, adequate delivery resources and fair administrative treatment. No fee amounts or jurisdiction-specific legal conclusions are invented in this publication.
Programme processes, real cases, impartiality, technical reliability, resources, public claims and verified improvement; not certificate volume alone.
Independent evaluation of the operator itself and any bounded use of another party results. The programme requirement does not establish external recognition or international acceptance.
Named programmes, disciplines, levels, curricula, campuses, partner/remote delivery and completion routes within F04. Programme recognition and individual occupational authority remain separate.
F08 C01-C06 with statement-specific boundary, period, methodology, assurance form and materiality. The competence of a verifier is evaluated separately from the truth of its statements.
Prospective transition, receiving capability, record and duty transfer, learner/customer protection and preservation of real historical decision bases.
Management Systems Assurance for 3 retained scope subjects. This book specifies evaluable implementation controls, scope boundaries and the complete application-specific parameter and evidence architecture. Actual engineering values, local permissions and release decisions must be separately established.
Critical Processes and Products for 22 retained scope subjects. This book specifies evaluable implementation controls, scope boundaries and the complete application-specific parameter and evidence architecture. Actual engineering values, local permissions and release decisions must be separately established.
Testing and Inspection for 10 retained scope subjects. This book specifies evaluable implementation controls, scope boundaries and the complete application-specific parameter and evidence architecture. Actual engineering values, local permissions and release decisions must be separately established.
Education Programmes for 6 retained scope subjects. This book specifies evaluable implementation controls, scope boundaries and the complete application-specific parameter and evidence architecture. Actual engineering values, local permissions and release decisions must be separately established.
Airports and Aerodromes for 5 retained scope subjects. This book specifies evaluable implementation controls, scope boundaries and the complete application-specific parameter and evidence architecture. Actual engineering values, local permissions and release decisions must be separately established.
Aircraft Maintenance and Technical Services for 7 retained scope subjects. This book specifies evaluable implementation controls, scope boundaries and the complete application-specific parameter and evidence architecture. Actual engineering values, local permissions and release decisions must be separately established.
Ground Operations and Aviation Support Services for 9 retained scope subjects. This book specifies evaluable implementation controls, scope boundaries and the complete application-specific parameter and evidence architecture. Actual engineering values, local permissions and release decisions must be separately established.
Carbon, Environment and Climate Assurance for 6 retained scope subjects. This book specifies evaluable implementation controls, scope boundaries and the complete application-specific parameter and evidence architecture. Actual engineering values, local permissions and release decisions must be separately established.
Requirement-level evaluation of the common core, provider/governance controls and integrated release gates. Source conditions are reproduced in full; every response requires attributable evidence, sampling and a reasoned conclusion. Family checklists are used with CL-001, the actual profile and all triggered normative annexes.
Requirement-level evaluation of Management Systems Assurance. Source conditions are reproduced in full; every response requires attributable evidence, sampling and a reasoned conclusion. Family checklists are used with CL-001, the actual profile and all triggered normative annexes.
Requirement-level evaluation of Critical Processes and Products. Source conditions are reproduced in full; every response requires attributable evidence, sampling and a reasoned conclusion. Family checklists are used with CL-001, the actual profile and all triggered normative annexes.
Requirement-level evaluation of Testing and Inspection. Source conditions are reproduced in full; every response requires attributable evidence, sampling and a reasoned conclusion. Family checklists are used with CL-001, the actual profile and all triggered normative annexes.
Requirement-level evaluation of Education Programmes. Source conditions are reproduced in full; every response requires attributable evidence, sampling and a reasoned conclusion. Family checklists are used with CL-001, the actual profile and all triggered normative annexes.
Requirement-level evaluation of Airports and Aerodromes. Source conditions are reproduced in full; every response requires attributable evidence, sampling and a reasoned conclusion. Family checklists are used with CL-001, the actual profile and all triggered normative annexes.
Requirement-level evaluation of Aircraft Maintenance and Technical Services. Source conditions are reproduced in full; every response requires attributable evidence, sampling and a reasoned conclusion. Family checklists are used with CL-001, the actual profile and all triggered normative annexes.
Requirement-level evaluation of Ground Operations and Aviation Support Services. Source conditions are reproduced in full; every response requires attributable evidence, sampling and a reasoned conclusion. Family checklists are used with CL-001, the actual profile and all triggered normative annexes.
Requirement-level evaluation of Carbon, Environment and Climate Assurance. Source conditions are reproduced in full; every response requires attributable evidence, sampling and a reasoned conclusion. Family checklists are used with CL-001, the actual profile and all triggered normative annexes.
Blank controlled record for Programme adoption and scope activation. The fields implement the common and module-specific payload in source Annex M and relevant expanded requirements. Complete only when the actual triggering activity occurs.
Blank controlled record for Application and requested scope. The fields implement the common and module-specific payload in source Annex M and relevant expanded requirements. Complete only when the actual triggering activity occurs.
Blank controlled record for Admission and evidence-reuse review. The fields implement the common and module-specific payload in source Annex M and relevant expanded requirements. Complete only when the actual triggering activity occurs.
Blank controlled record for Technical-profile and criterion schedule. The fields implement the common and module-specific payload in source Annex M and relevant expanded requirements. Complete only when the actual triggering activity occurs.
Blank controlled record for Competence, experience and authorisation. The fields implement the common and module-specific payload in source Annex M and relevant expanded requirements. Complete only when the actual triggering activity occurs.
Blank controlled record for Case conflict and assignment. The fields implement the common and module-specific payload in source Annex M and relevant expanded requirements. Complete only when the actual triggering activity occurs.
Blank controlled record for Assessment plan and time. The fields implement the common and module-specific payload in source Annex M and relevant expanded requirements. Complete only when the actual triggering activity occurs.
Blank controlled record for Remote-method suitability and session. The fields implement the common and module-specific payload in source Annex M and relevant expanded requirements. Complete only when the actual triggering activity occurs.
Blank controlled record for Witness and vertical technical trail. The fields implement the common and module-specific payload in source Annex M and relevant expanded requirements. Complete only when the actual triggering activity occurs.
Blank controlled record for Evidence and sample index. The fields implement the common and module-specific payload in source Annex M and relevant expanded requirements. Complete only when the actual triggering activity occurs.
Blank controlled record for Technical result and measurement decision. The fields implement the common and module-specific payload in source Annex M and relevant expanded requirements. Complete only when the actual triggering activity occurs.
Blank controlled record for Finding, containment and corrective action. The fields implement the common and module-specific payload in source Annex M and relevant expanded requirements. Complete only when the actual triggering activity occurs.
Blank controlled record for Independent review and decision. The fields implement the common and module-specific payload in source Annex M and relevant expanded requirements. Complete only when the actual triggering activity occurs.
Blank controlled record for Scope schedule and certificate instruction. The fields implement the common and module-specific payload in source Annex M and relevant expanded requirements. Complete only when the actual triggering activity occurs.
Blank controlled record for Surveillance, change and renewal. The fields implement the common and module-specific payload in source Annex M and relevant expanded requirements. Complete only when the actual triggering activity occurs.
Blank controlled record for Suspension, restriction, restoration and withdrawal. The fields implement the common and module-specific payload in source Annex M and relevant expanded requirements. Complete only when the actual triggering activity occurs.
Blank controlled record for Complaint, appeal and protected disclosure. The fields implement the common and module-specific payload in source Annex M and relevant expanded requirements. Complete only when the actual triggering activity occurs.
Blank controlled record for Operator agreement and authorisation schedule. The fields implement the common and module-specific payload in source Annex M and relevant expanded requirements. Complete only when the actual triggering activity occurs.
Blank controlled record for Laboratory/inspection competence and validity. The fields implement the common and module-specific payload in source Annex M and relevant expanded requirements. Complete only when the actual triggering activity occurs.
Blank controlled record for Process qualification and product readiness. The fields implement the common and module-specific payload in source Annex M and relevant expanded requirements. Complete only when the actual triggering activity occurs.
Blank controlled record for Education self-study and outcome attainment. The fields implement the common and module-specific payload in source Annex M and relevant expanded requirements. Complete only when the actual triggering activity occurs.
Blank controlled record for Airport and operational-interface dossier. The fields implement the common and module-specific payload in source Annex M and relevant expanded requirements. Complete only when the actual triggering activity occurs.
Blank controlled record for Maintenance facility/type/task capability. The fields implement the common and module-specific payload in source Annex M and relevant expanded requirements. Complete only when the actual triggering activity occurs.
Blank controlled record for Station/service and local-variation dossier. The fields implement the common and module-specific payload in source Annex M and relevant expanded requirements. Complete only when the actual triggering activity occurs.
Blank controlled record for Environmental statement and verification. The fields implement the common and module-specific payload in source Annex M and relevant expanded requirements. Complete only when the actual triggering activity occurs.
Blank controlled record for Digital evidence, incident and recovery. The fields implement the common and module-specific payload in source Annex M and relevant expanded requirements. Complete only when the actual triggering activity occurs.
Blank controlled record for Internal audit, management and independent operator review. The fields implement the common and module-specific payload in source Annex M and relevant expanded requirements. Complete only when the actual triggering activity occurs.
Blank controlled record for Programme change, transition and closure. The fields implement the common and module-specific payload in source Annex M and relevant expanded requirements. Complete only when the actual triggering activity occurs.
PDF record architecture, field dictionary, manual review rules and blank capture sheets for Applicant, Scope and Case Register. This replaces only the planned delivery format for this issue: it is not an executable spreadsheet, access-control system, database or automatic decision engine.
PDF record architecture, field dictionary, manual review rules and blank capture sheets for Personnel, Authorisation and Conflict Register. This replaces only the planned delivery format for this issue: it is not an executable spreadsheet, access-control system, database or automatic decision engine.
PDF record architecture, field dictionary, manual review rules and blank capture sheets for Technical Methods, Equipment and Validity Register. This replaces only the planned delivery format for this issue: it is not an executable spreadsheet, access-control system, database or automatic decision engine.
PDF record architecture, field dictionary, manual review rules and blank capture sheets for Evidence, Findings and Corrective Action Register. This replaces only the planned delivery format for this issue: it is not an executable spreadsheet, access-control system, database or automatic decision engine.
PDF record architecture, field dictionary, manual review rules and blank capture sheets for Outcome Status, Claims and Registry Change Register. This replaces only the planned delivery format for this issue: it is not an executable spreadsheet, access-control system, database or automatic decision engine.
PDF record architecture, field dictionary, manual review rules and blank capture sheets for Education and Environmental Programme Records. This replaces only the planned delivery format for this issue: it is not an executable spreadsheet, access-control system, database or automatic decision engine.
PDF record architecture, field dictionary, manual review rules and blank capture sheets for Governance, Profile Release and Improvement Register. This replaces only the planned delivery format for this issue: it is not an executable spreadsheet, access-control system, database or automatic decision engine.
Role-specific competence, technical coverage, witnessing and productive assessment resources across the actual programme scope.
Versioned participation and operator-service terms, fee categories, local conditions and commercial responsibilities without outcome-linked incentives.
Controlling notifications, deadlines, retention, date arithmetic and consequences; genuine event and completion records remain separate.
Actual authority, higher-instrument compatibility, normative process and exact-profile activation, with no automatic adoption from publication.
Try a broader subject, document code or another group.
One copy per controlled code is listed. The supplied root-level standard is byte-identical to AF-AST-STD-001. Forms are blank controlled records; registers are PDF architectures and capture sheets, not a live database or automated decision system.
Scope & technical enquiries
Describe your role, technical activity, site and intended outcome. Ask about current scope availability and the applicable requirements before treating a document as an open assessment route.
