Machine authorizations
The Planche knows which machines each pilot is released on. It uses this to warn (or block, depending on the club's choice) when a pilot declares a flight on a machine they aren't authorized on.
What an authorization is
- It covers a model (for example "ASK21"): every machine of that model is covered, including a machine that arrives later;
- or one specific machine (private machine, special configuration).
- A private machine's owner is authorized on their own machine.
Its status
| Status | Meaning |
|---|---|
| Active | The pilot flew this model recently (or was just released) |
| To revalidate | No flight on this model for the club's delay (12 months by default): a check flight with an instructor is needed |
| Revoked | Withdrawn by an instructor or the administrator, with a reason |
The last flight date is updated automatically on every validated flight, for the pilot in command: the instructor on an instruction flight, both pilots on a shared flight, the pilot otherwise.
When declaring a flight
Once the pilot is chosen, the machine list shows:
- authorized machines first;
- "to revalidate" or "not authorized" next to the others.
If the chosen machine is an issue, a message shows below it. Depending on the club's setting:
| Setting | Effect |
|---|---|
| Off | Nothing is checked |
| Warn (default) | The message shows, but the flight is accepted |
| Block | A solo, shared, passenger or trial flight is refused |
Instruction, first solo and supervised flights are never checked: that is precisely how a pilot gets released on a new machine.
Releasing, revalidating, revoking (instructors)
From today's Planche, Ratings tab (member portal, "Planche management"), the instructor picks a present pilot; their authorizations show up:
- Grant: by model or for one machine — for example right after the release flight;
- Revalidate: after the check flight, for an authorization "to revalidate";
- Revoke: with a required reason (history stays visible with "Show revoked").
The administrator has the same panel on the pilot sheet (Pilots → ratings).
Settings (administrator)
In Comportement des vols (flight behaviour), Machine authorizations section:
- the check when declaring: off, warn or block;
- the delay before revalidation, in months (12 by default);
- Pre-fill from the ERP history: creates one authorization per pilot and model flown as pilot in command since the chosen date (24 months by default), with the last flight date. Existing authorizations are kept; it can safely be run again.
Over time
- Authorizations don't depend on the flight history kept by the Planche (purged after transfer to the ERP): only the last flight date is kept.
- A pilot who stops flying sees their authorizations become "to revalidate".
- When a member is anonymised in the ERP, their authorizations are deleted with them.