A simulator failing in the middle of a type rating course does not, by itself, invalidate anything. The sessions already flown stay flown, the signatures stay valid and the syllabus stays approved. What an outage attacks is something less visible: the spacing between sessions, and a set of validity dates that keep running while the hydraulics are apart. Courses very rarely break on the day of the failure. They break three weeks later, when a date nobody was watching expires.
Two approvals, and only one of them has stopped
Every simulator session sits at the intersection of two separate documents, and confusing them is the source of most of the panic in the crew room.
The first is the qualification of the device itself. A full flight simulator or a flight training device is qualified by a competent authority against a fidelity standard, on the basis of a qualification test guide and a set of recurring evaluations. That qualification says what the machine may be used to represent, and at what level. It belongs to the device.
The second is the approval of the course. An approved training organisation holds an approval for a training programme, and that programme specifies which exercises are flown in which class of device, in which order, with which instructor qualifications. That approval belongs to the organisation, not to the machine.
When a device goes unserviceable, the first document is affected and the second is not. The syllabus has not changed, the trainee’s progress has not changed, and nothing in the training record becomes retroactively invalid. What has happened is narrower and entirely practical: one particular resource named in a schedule is unavailable. The whole art of continuity management is keeping that distinction clear while the phone rings.
What an outage touches, and what it does not
| Element | Status | Who decides |
|---|---|---|
| Exercises flown, assessed and signed in the training record | Unaffected. They remain part of the completed course | Nobody — the record is the record |
| A session interrupted part-way through | Credited for what was completed and assessed; the rest is rescheduled | The instructor conducting it, then the head of training |
| The remaining syllabus | Unchanged in content and sequence | The approved course, not the scheduler |
| The device’s qualification | Restricted or suspended for the exercises that depend on the failed function | The device operator, against the qualification conditions, with the authority informed where required |
| The instructor’s and examiner’s authorisations | Unaffected by the outage, but they carry their own expiry dates | The competent authority and the organisation’s records |
| The trainee’s medical and licence privileges | Unaffected by the outage, and still counting down | Calendar |
Note the asymmetry in the middle row. A device can very often be operated with some functions deferred: a failed weather radar display does not prevent a raw-data non-precision approach exercise, but it does prevent anything that credits the use of that display. The device operator’s discrepancy log exists exactly to make that judgement traceable, exercise by exercise, rather than treating the machine as binary.
The trap. A device that is technically serviceable but operating with a deferred discrepancy is not automatically usable for every exercise in your syllabus. Ask which functions are affected and cross-check them against the session content, before the crew is briefed rather than after.
The four ways to keep a course moving
Continuity is not one procedure. It is four options with very different administrative weight, and the mistake is reaching for a heavy one when a light one would do.

| Option | What it needs | What it costs |
|---|---|---|
| Same device, later slot — night hours, a weekend, a gap in another customer’s booking | Nothing beyond a schedule change and crew duty compliance | Fatigue management, and the goodwill of everybody’s roster |
| A sister device on the same site, same type and qualification level | Verification that the configuration matches the course’s device requirements; a briefing on any differences in avionics standard or engine variant | Usually little, provided the device is already named in the organisation’s approval |
| A device at another site or another operator | The device must be covered by the training organisation’s approval or a contracted arrangement; the instructor must be authorised for that device; travel and duty time for everyone | Significant. This is where most of the delay and most of the money go |
| Reordering the syllabus, or moving eligible content to a lower-level device | Only what the approved course already permits. Anything else is a change to an approved programme | Free if it is already allowed, weeks if it is not |
The fourth row is the one people get wrong under pressure. If the approved programme says an exercise is flown in a full flight simulator, moving it to a flight training device is not a scheduling decision made by a duty manager. It is a departure from an approved course. If the programme already names a permitted alternative, the substitution is legitimate and immediate; if it does not, the only route is a change to the approved programme agreed with the authority, and that takes longer than the outage usually lasts.
Reordering, by contrast, is often available and under-used. Most syllabi are only partly gated. Handling exercises generally have to precede the line-oriented flight training that assumes them, and the skill test comes last by definition, but within the earlier blocks there is frequently more freedom than the printed schedule suggests. Establishing which sessions are truly sequence-dependent before an outage happens is a half-day of work that pays for itself the first time a pump fails.
Where the course actually breaks: the interval
The genuine limit is not the failure. It is the gap between sessions.
Type rating training works because sessions are close enough together that each one builds on a skill still warm from the last. Stretch the interval and the next session is spent recovering ground rather than gaining it. Training organisations know this and write maximum intervals between sessions into their course documentation — the figure varies by organisation, by type and by phase of the course, and it lives in the approved programme rather than in any single regulation.
Exceed it and two things happen. Operationally, the instructor will have to repeat content, which consumes hours the contract may not include. Administratively, the head of training has to make and record a decision: continue with additional refresher content, or repeat a defined block of the course. That decision is the one that costs money, and it is a competence judgement, not a paperwork formality.
This is why the practical question after an outage is never “when can we get back in?” but “how long is the gap, and where does it fall?”. A four-day gap between two handling sessions early in the course is an inconvenience. The same gap immediately before the line-oriented flight training, or between the last training session and the skill test, is a different problem entirely, because those sessions assume a consolidated skill set rather than a fresh one.
The real problem isn’t the simulator breaking, but the time lost between sessions. If the gap is too long, the trainee may need to repeat parts of the course, which costs time and money. The key is to keep sessions close together to maintain learning momentum.
An A320 type rating course has a maximum 7-day interval between handling sessions. If a simulator fails for 5 days, the next session can proceed without extra training. But if the failure lasts 10 days, the trainee must repeat the previous session, adding 2 extra hours to the course and delaying the skill test.
The clocks that keep running
An outage is dangerous mostly because of what it does to dates that don’t stop. Every one of these is running while the device is being repaired, and none of them stops out of sympathy.
| Clock | What it governs | Who can move it |
|---|---|---|
| Theoretical knowledge credit for the associated licence or rating | Whether the training can still count towards the intended licence action | Nobody. The validity period is set in the licensing rules |
| The window between completion of training and the skill test | Whether the course has to be partly repeated before the test | Set by the licensing rules and the approved course |
| The maximum interval between sessions | Whether refresher content or a repeated block is required | The head of training, within the approved course |
| Medical certificate validity | Whether the trainee may fly the test at all | Nobody, though an examination can be brought forward |
| Existing rating, proficiency check or operator check validity | Whether a revalidation is still possible or a renewal becomes necessary | Nobody. This is the expensive one |
| Recent experience for carrying passengers — three take-offs, approaches and landings in the preceding ninety days | Whether line flying can resume immediately after the course | Regained by flying, or in an appropriately qualified device |
The fifth row deserves its own paragraph, because it is where an outage stops being a scheduling problem and becomes a licensing one.
The recurrent case: a check that has to happen before a date
Initial courses have flexibility. Recurrent checks do not, and a simulator failing in the last fortnight of a validity period is a materially different event from one failing in week two of a type rating.
Under Part-FCL the distinction that matters is between revalidation and renewal. A proficiency check flown while the rating is still valid revalidates it, and when it is flown inside the defined period immediately before expiry the new validity is counted from the existing expiry date rather than from the day of the check — so nothing is lost by being early. Let the rating expire and revalidation is no longer available: renewal is the only route left, an approved training organisation assesses what refresher training is needed to bring the pilot back to standard, and a proficiency check follows. The cost difference between the two routes is not marginal.
The regulatory architecture is not the same everywhere. Operations under FAA rules organise recurrent training and checking around base months, with defined grace either side, which builds a degree of latitude into the calendar. The EASA scheme has its own mechanisms — validity periods that run on past the month of issue, and a window before expiry that preserves the original date — but they are different mechanisms with different edges, and any alleviation for an exceptional circumstance is granted by the competent authority rather than assumed by the operator. Do not carry an assumption across from one system to the other.
The right reflex. The moment a device is declared unserviceable, the first list to produce is not the list of cancelled sessions. It is the list of expiry dates belonging to every crew member booked on that device for the next month, sorted by date. Whoever is closest to an expiry gets the first replacement slot, whatever the original booking order said. Scheduling by original booking order is how an operator turns a three-day outage into two renewals and a grounded captain.
Who decides, and what has to be written down
Continuity decisions belong to named people. In an approved training organisation, the head of training owns the judgement on whether a course can continue as planned, needs additional content, or requires a block to be repeated. The instructor conducting the interrupted session owns the assessment of what was actually completed and to what standard. The device operator owns the statement of what the machine may and may not be used for. Nobody else’s opinion has any status, however senior.
Three things have to end up in the training file, and their absence is what an audit finds later: the fact and duration of the interruption, the decision taken on continuity and by whom, and any additional or repeated content flown as a result. A file showing an eleven-day gap with no annotation invites exactly the question the organisation will least want to answer — whether anybody looked.
What a trainee should ask for
For a self-funded type rating, an outage is also a commercial event, and the contract is usually more explicit than trainees expect. Three questions are worth asking in writing rather than in a corridor: what the revised schedule is and against which device, whether any additional sessions arising from the interruption are chargeable, and what the arrangement is if the replacement slot falls outside the period the course was sold for. Organisations that answer those clearly are the ones worth training with; the answers are also a fair proxy for how the organisation handles everything else. Candidates comparing providers before committing will find the question worth putting directly, alongside the usual ones about instructor stability and device availability — the sort of ground covered in the FL330 training resources.
None of this is exotic. Simulators are complex machines run at high utilisation, and unserviceability is a normal operating condition rather than a crisis. Organisations that treat it as normal keep a spare slot in the week, know which sessions can be resequenced, and watch expiry dates rather than booking order. Organisations that treat it as a crisis discover the interval limit and the validity dates at the same time, which is the expensive way to learn both.

Leave a Reply
You must be logged in to post a comment.