Scope-defined competence
Confidence in a specific activity. Not a blanket endorsement.
Accreditation assesses the competence and consistent operation of laboratories, inspection bodies, certification bodies and specialist technical organizations within defined scope.
Prepare the initial activity profile
Preparing an Accreditation scope.
A clear initial profile explains the work actually performed, the locations involved and the technical boundary requested. Initial review confirms the applicable route and assessment basis.
Give the activity a concrete description
- Activity
- What do you test, calibrate, inspect, certify or evaluate?
- Technical boundary
- Which methods, criteria, subjects and operating locations are relevant?
- Responsible capability
- Which personnel, resources and controlled records support that work?
- Clarification
- What is specialized, cross-route or not yet sufficiently defined?
ASTRA / F01–F08
Eight programmes.
Precisely defined scopes.
Choose the programme family that matches the work. The technical object, assessment activity and authorized outcome remain distinct.
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.
Explore programmeCritical Processes and Products
Connect the actual product or process configuration to design, qualification, manufacturing and release evidence. Critical activities require application-specific criteria and demonstrated technical coverage.
Explore programmeTesting and Inspection
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.
Explore programmeEducation Programmes
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.
Explore programmeAirports and Aerodromes
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.
Explore programmeAircraft Maintenance and Technical Services
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.
Explore programmeGround Operations and Aviation Support Services
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.
Explore programmeCarbon, Environment and Climate Assurance
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.
Explore programmeA programme family is not a blanket approval. The applicable profile, approved scope and current public record determine what a particular outcome covers. Publication of a profile is not activation of every service.
Read the ASTRA frameworkScope architecture
Five dimensions make one claim understandable.
A scope-defined assessment cannot be read as approval of everything an organization does. Expand a dimension to understand what it identifies.
01Entity
Identify the legal entity and the relevant facility or organizational boundary. A parent-company name cannot substitute for the entity actually assessed.
02Activity
Name the testing, calibration, inspection, certification or specialist activity. “Aerospace services” is too broad to explain the competence conclusion.
03Method & subject
State the methods or criteria and the subjects to which the activity applies. A sector label does not replace this technical boundary.
04Location
Identify the applicable operating locations and facility context. Do not assume an approval applies to every branch or outsourced location.
05Status & limits
Read the approved scope, current status, dates and any limitations together. An application or old certificate is not a substitute for the current public record.
Assessment and decision
The scope is proposed. The conclusion is earned through evidence.
- Define
Application & scope review
Describe identity, activity, locations and the requested technical boundary. The route and assessability are reviewed.
- Examine
Planning & technical assessment
Relevant references, competence and sampling inform document review, discussion, observation and witnessing where appropriate.
- Decide
Findings & independent review
Corrective evidence, independent review and the authorized decision determine whether—and for what scope—Accreditation is granted.
- Maintain
Public record & oversight
Where granted, the record states status, dates and scope. Surveillance and change review support continuing confidence.
Separate institutional relationships
Do not substitute one status for another.
- Membership
- A participation relationship—not assessed competence.
- Recognition
- A separate scope-specific acknowledgement for eligible active members.
- Accreditation
- Competence for defined assessment or specialist activities—not regulatory permission to operate.
- Certification
- A distinct conformity conclusion under an applicable scheme—not interchangeable with Accreditation.
Make the requested scope clear.
Organizations with established or emerging aerospace activities can submit a proposed scope for initial review. An application is not an approval.