The Certificate of Recognition (CoR), documented on EASA Form 148, is the formal certification that a student has successfully completed an approved basic training course at a Part 147 maintenance training organisation. It is the key deliverable of your training programme — and the document that NAA inspectors scrutinise most carefully during audits.
Getting it wrong has consequences: an invalidly issued CoR can lead to regulatory findings, suspension of issuance privileges, and — in the worst case — affect the validity of licences issued to your graduates.
This article explains what the CoR certifies, what prerequisites must be verified before issuance, and how purpose-built software eliminates the risk of non-compliant certificate generation.
What the Certificate of Recognition Certifies
A CoR issued under EASA Part 147 certifies that the named individual has:
- Completed all theoretical knowledge examinations for the relevant Part 66 modules, achieving the required pass marks
- Met minimum attendance requirements for the approved training programme
- Completed all required practical assessments — typically the P1–P9 workshop skill areas defined in the approved syllabus
- Satisfied any additional prerequisites defined in the MTO's approved training programme (MTOE)
The CoR is not a licence — it is one of the prerequisites for a student to apply for a Part 66 aircraft maintenance licence from their national aviation authority.
EASA Form 148 — Format Requirements
The CoR must be issued using EASA Form 148, which defines a specific format including:
- The MTO's Part 147 approval reference number
- The student's full name and date of birth
- The category and sub-category of the training completed (e.g., B1.1, B2)
- The Part 66 modules covered, with examination results
- A unique certificate reference number
- Date of issuance and authorised signatory
Any deviation from the Form 148 format can result in the certificate being rejected by the NAA when the student applies for their licence. This is why manual certificate generation — using Word templates or similar — creates unnecessary risk.
The Pre-Issuance Checklist — What Must Be Verified
Before issuing a CoR, your quality system should require verification of the following:
- All module examinations passed — every Part 66 module in the approved syllabus must show a pass result
- No outstanding re-sits — if a student failed and re-sat a module, the re-sit result must be recorded
- Attendance threshold met — the student must have met the minimum attendance percentage defined in the MTOE
- Practical assessments complete — all P1–P9 workshop skills (for basic training) must be signed off by a qualified assessor
- No administrative holds — tuition fees paid, disciplinary actions resolved, etc.
- Document verification — entry qualifications and identity documents are on file
In a manual system, this checklist is performed by a staff member reviewing multiple sources — exam spreadsheets, attendance logs, practical assessment forms. Each cross-reference is an opportunity for error.
Common CoR Issuance Mistakes
Based on common NAA audit findings, the most frequent CoR-related issues are:
- Issuing a CoR before all modules are passed — typically caused by a missed re-sit record or a module marked "pass" in one system but "fail" in another
- Incorrect module listing — the CoR lists modules that don't match the approved programme, or omits modules
- Missing attendance verification — the student's attendance was not checked against the minimum threshold before issuance
- Certificate numbering gaps — the certificate registry has gaps or duplicate numbers, suggesting poor control
- Unsigned or incorrectly signed certificates — the signatory is not an authorised person per the MTOE
How Software Automates Compliant CoR Generation
Purpose-built Part 147 software like AMTOS eliminates these risks by making the CoR a computed output rather than a manually assembled document:
- Automatic prerequisite validation — the system checks every requirement (exams, attendance, practicals) before the "Generate CoR" button becomes available. If any prerequisite is unmet, the system blocks issuance and displays the specific gap.
- EASA Form 148 template — certificates are generated using a compliant template that pulls data directly from the student's training record. No manual typing, no format errors.
- One-click PDF generation — the completed Form 148 is rendered as a print-ready PDF in seconds.
- Automatic registry — every issued certificate is assigned a sequential reference number and logged in a searchable registry with issuance date, signatory, and student reference.
- Audit trail — the system records who generated the certificate, when, and what data was used — providing complete traceability for NAA inspectors.
The fundamental shift is from a process that relies on human diligence (checking multiple sources, filling in templates) to one that relies on system enforcement (the software won't let you issue an invalid certificate).
The Bottom Line
The Certificate of Recognition is the culmination of your entire training programme. It represents months of instruction, examination, and assessment — and it must be right. Manual CoR processes introduce risk at every step. Software-driven CoR generation doesn't just save time — it protects the integrity of every certificate your MTO issues.