Definition
Refresher training is the remedy for a gap. Where recurrent training maintains a qualification that is still current, refresher training addresses the case where the person has been away — through absence, secondment, parental leave, illness, or simply not having operated a type for a period — and their currency no longer stands on its own.
For cabin crew the requirement is at ORO.CC.145, sitting immediately after recurrent training at ORO.CC.140 in the same subpart, and alongside the conduct of training and checking at ORO.CC.115. The equivalent concept exists for flight crew, where a pilot returning after an extended absence completes refresher training before resuming line operations, and in maintenance, where an organisation's procedures set out what a certifying staff member does after a period without exercising their authorisation.
The content is not a repeat of initial training. It is targeted at what decays: the practical, time-sensitive elements — emergency procedures, equipment operation, drills — rather than the underlying knowledge that does not fade the same way. The length and content depend on how long the gap was, which is why refresher requirements are usually expressed as tiers rather than a single course.
The administrative difficulty is that refresher training is triggered by an absence, and absences are recorded in a different system from training. A training record shows when somebody last completed an item; it does not, by itself, show that they have not operated since. An organisation therefore needs to connect three things that are often kept apart: the training record, the operating record, and the roster. Where those are separate, a returning crew member's refresher requirement tends to be identified by a manager who happens to remember, rather than by the system.
Getting this wrong is expensive in both directions. Missing a refresher requirement means someone operates without the currency the rule demands. Applying one unnecessarily consumes training capacity that was already tight.
Refresher requirements are normally tiered by the length of the gap, because a month away and a year away do not decay the same competencies. A short absence may need little more than familiarisation under ORO.CC.135 before resuming; a long one can require the practical safety and emergency elements to be repeated and checked before the person is assignable again. The tiering is set out in the operator's own training and checking programme, which means the same absence can produce different obligations at different operators — and that the programme, not just the regulation, is what an auditor reads.
Why It Matters for Flight Schools
Refresher training is the part of a training programme that cannot be planned from a calendar, because it is driven by events rather than dates. That makes it structurally different from recurrent training and harder to resource: demand appears when somebody returns, not on a schedule.
It is also the case where the record is most likely to be incomplete. A crew member returning from a long absence has a training file that looks superficially fine — the last recurrent item may still be within its cycle — while the operational fact is that they have not flown for months. Whether the refresher obligation bites depends on information the training record does not hold.
Organisations that handle returns well tend to treat the return itself as a trigger, with a defined path back to the line, rather than as an administrative event that happens to require some training.
How Aviatize Handles This
Because Aviatize holds training records, qualifications and bookings in the same system, a crew member's last completed training item and their last actual operation are both visible on one record rather than sitting in separate systems that nobody reconciles.
Refresher courses are configured as their own course structures with their own events and checks, so the path back to the line is defined and evidenced rather than improvised, and completion updates the same validity tracking that governs assignability.
The Validation Engine's preconditions mean a crew member whose currency does not support assignment is caught at the point of booking, which is the practical safeguard for the case where an absence was longer than anyone realised.