The sector challenge
A useful development opportunity needs more than a match.
Students and emerging professionals need an appropriate problem, competent support, access to suitable information and a way to demonstrate what they have learned. Employers and universities need clear responsibilities, realistic supervision demands and a defined relationship with their own educational or employment processes.
Development covers mentoring, capstone projects and internship frameworks as distinct learning formats. The work connects technical objectives with matching criteria, supervision, progress reviews and a meaningful final output, keeping educational responsibilities visible throughout.
Programme development priorities
- Map a technical learning need to a suitable discipline and format.
- Define participant, mentor, academic and host responsibilities.
- Review learning through evidence, feedback and an agreed technical output.
Technical scope & method
A structured approach to the question.
- 01Competency and matching
- Identify the aerospace discipline, starting knowledge, intended competencies and support needs. Match against technical relevance, availability and conflicts, rather than relying on profile keywords alone.
- 02Challenge design
- Translate an industry-defined engineering question into a capstone or mentoring brief with realistic learning objectives, authorized information and achievable deliverables.
- 03Supported progress
- Define meeting arrangements, progress records, escalation routes and review points. Researcher and expert exchanges follow explicit objectives, institutional responsibilities and progress reviews.
- 04Learning review
- Assess the technical output against the original objectives and collect participant and mentor feedback. Separate educational achievement from employment selection or professional certification.
- 01Learning objectivesCompetency and starting knowledge
- 02Matched supportRoles, supervision and permissions
- 03Technical challengeProgress and feedback records
- 04Learning reviewOutput and demonstrated understanding
Pilot development & application
A small university–industry capstone or mentoring exercise.
The capstone-development framework uses a defined engineering task, such as comparing maintenance-access considerations in a reference equipment layout. Authorized or synthetic engineering information supports requirements analysis, design reasoning and review. Learning evidence is assessed separately from decisions about a real aircraft design or maintenance release.
Agree the learning brief
Set the technical question, deliverable, supervision commitments and assessment criteria with the relevant academic or host institution.
Review in stages
Use a requirements review, a method review and a final explanation of assumptions. Record feedback and how it changed the work.
Evaluate the outcome
Review completion, technical reasoning and participant feedback. Decide whether the format is worth developing before considering any wider intake.
Development connects a defined application, measurable criteria and a traceable technical review.
Technical deliverables
Outputs and evaluation.
The development workstreams connect these deliverables to reviewable evidence and application-specific evaluation criteria.
- Participant and mentor role definitions
- Competency framework
- Capstone or mentoring project brief
- Progress review structure
- Participant feedback report
- Learning outcomes assessment
Evaluation priorities
- Learning achievement
- Evidence against the agreed competencies, not simply attendance.
- Technical output
- Quality of reasoning, treatment of assumptions and usefulness of the final deliverable.
- Programme suitability
- Completion, supervision demands, participant feedback and identified improvements.
Participation & boundaries
The right expertise. Clear responsibilities.
The participation framework defines the roles of students, emerging specialists, academic supervisors, experienced professionals and host organizations. Matching considers technical relevance, support needs, availability and the responsibilities of the learning setting.
Scope and safeguards
Privacy, safeguarding, educational and employment requirements are addressed through the responsibilities of participating institutions. Supervision, permitted information use and escalation arrangements form part of the programme framework.
Professional learning, membership and Secretariat employment are separate relationships. Placement and employment conditions belong to the relevant host and academic arrangements.
Participation and technical decisions remain separate.
Participation does not automatically confer membership rights, AF Recognition, accreditation, certification, standards-setting authority or procurement preference. Sponsorship must not determine technical conclusions, evaluation results or governance decisions.
Development pathway
Development, grounded in evidence.
Technical objectives, responsible coordination and application needs shape the development process. Resources, safety, confidentiality, data protection, intellectual property and reporting arrangements are reviewed alongside the methods and deliverables, keeping progress focused and accountable.
A structured development pathwayExplore the seven connected development stages
Programme development connects technical requirements, responsible coordination and reviewable evidence. Each stage informs the next, while review findings refine the scope, methods and priorities.
- Requirements & Objectives
Define the technical problem, user need and scope.
- Feasibility & Evidence
Examine methods, resources, interfaces and dependencies.
- Scope & Responsibilities
Align workstreams, coordination and review arrangements.
- Pilot Development
Connect the evaluation plan to funding, safety, data and intellectual-property controls.
- Controlled Implementation
Maintain the agreed technical boundary and responsible delivery arrangements.
- Technical Evaluation
Review evidence and outcomes against application-specific criteria.
- Knowledge & Further Development
Translate reviewed findings into useful outputs and the next development priorities.