Aircraft lifecycle
An Envergure aircraft moves through seven canonical statuses between its arrival and its removal from the fleet. Some statuses are driven directly by an administrator from the aircraft sheet (move to storage, transfer, retirement); others are governed by the lifecycle of an enrolment Work Package (WP) and cannot be edited by hand. This page explains who changes what, and why.
The seven statuses
| Status | Technical key | Business meaning |
|---|---|---|
| To enrol | to_enrol |
Aircraft created, waiting for the enrolment dossier to be opened. |
| Enrolment in progress | in_enrolment |
An enrolment WP is active — the technical team is capturing the configuration. |
| In service | in_service |
Flight-ready, active limits, schedulable. |
| In maintenance | maintenance |
A curative, preventive or mixed WP is in progress. |
| In storage | storage |
Pulled out of operations without being retired. |
| Transferring | transferring |
Moving to another site or operator. |
| Retired | retired |
Definitive fleet exit, kept for traceability. |
Why “To enrol” and “Enrolment in progress” are not editable by hand
These two statuses reflect a verifiable business fact: an enrolment dossier has been opened, or not. Letting them be edited by keyboard would break that guarantee — an aircraft could be declared “In service” without an applied configuration ever being captured, which Part-145 and EMAR/FR auditors will not accept.
The aircraft edit form therefore hides these two options and shows the current status read-only when the aircraft is in an enrolment phase. The transitions are automatic when the matching WP is opened or closed.
How to start an enrolment
Create the aircraft, then enrol it
- Create the aircraft
On /fleet/new, capture the registration, serial number (MSN) and product version. The aircraft is born in the To enrol status (Prisma default). API: POST
/aircraft. - Open the enrolment dossier
From the aircraft sheet, click “Enrol aircraft”. The modal creates a WP of kind
enrolmentattached to a workshop. The WP is created indraft, then moved toin_progressfrom the Workbench. On that transition the aircraft automatically moves to Enrolment in progress. - Capture the applied configuration
The Workbench lets you initialise the applied configuration from the source decomposition, then capture SNs component by component, along with the initial counters (hours, cycles).
How to finish an enrolment
Clicking “Terminate maintenance” in the Workbench triggers the completed transition
of the enrolment WP. The aircraft automatically moves to In service, and its
commissioning date (commissioningDate) is set to today’s date if it was not entered
manually.
From that moment on, the aircraft is schedulable: its calendar and counter limits become active and it can enter the maintenance scheduler.
What happens if an enrolment in progress is cancelled?
If an enrolment WP is cancelled while it was already in_progress, the aircraft
automatically goes back to To enrol. This is an explicit rollback: an
aircraft must never be left in limbo as “Enrolment in progress” with no active WP behind it.
How to re-enrol an aircraft
An aircraft in In service, In storage or Transferring can be sent back to To enrol through an admin action: the route
POST/aircraft/:id/mark-to-enrol (guarded by an admin guard). Real-life
cases:
- transfer from another unit with full inventory recapture,
- return from a heavy industrial overhaul that disrupted the configuration,
- regulatory audit asking to re-trace the original configuration.
The action refuses to execute if a WP is currently active on the aircraft (close or cancel it
first) or if the source status is not allowed (refused from in_enrolment,
maintenance, retired, or to_enrol itself).
Full transition matrix
For developers and auditors who want the exhaustive view:
| Transition | Who triggers it |
|---|---|
(creation) → to_enrol |
Prisma default on aircraft creation. |
to_enrol → in_enrolment |
Enrolment WP moving to in_progress (business cycle). |
in_enrolment → in_service |
Enrolment WP closure (completed) — auto-set of the commissioning date. |
in_enrolment → to_enrol |
Cancellation of an enrolment WP that was in_progress — rollback. |
in_service ↔ maintenance |
Opening / closing / cancelling a curative, preventive or mixed WP. |
in_service ↔ transferring |
Direct PATCH on the aircraft sheet (admin). |
* → retired |
Direct PATCH on the aircraft sheet (admin). |
transferring → to_enrol |
Admin action POST /aircraft/:id/mark-to-enrol (re-enrolment). |
Every transition is recorded in the immutable audit log: the corresponding event is
aircraft.status_transitioned (WP-triggered) or aircraft.marked_to_enrol (admin action), with
the timestamp, the actor and the cause.
See also
- Fleet management — list, map and sheet views.
- Maintenance workbench — where WPs are driven.
- Work packages — list of in-progress WPs.