Setting up a maintenance programme
How to author an aircraft's maintenance programme in FlyerOS, its requirements and intervals, so the due-list and the schedule keep it airworthy.
Last reviewed
An aircraft's maintenance programme is the set of things that must be done to keep it airworthy, and how often. In FlyerOS the programme is structured data, so the due-list and the schedule read it directly rather than someone reading a PDF and remembering.
Start from a template, or your own
FlyerOS ships a set of starter programmes for common UK GA types. Start from one and adjust it, or build a programme from scratch. Either way you are editing structured requirements, not a document.
Requirements and intervals
Each programme is a list of requirements (a 50-hour check, an annual, an oil change), and each requirement has an interval expressed in the terms that actually apply:
- Hours flown, cycles or landings, and calendar time, singly or in combination.
- A tolerance band where one is allowed.
- "Whichever comes first" when more than one interval applies.
Intervals are shown back to you in plain English, so "every 50 flying hours or 12 months, whichever is first, with a 10% tolerance" reads as exactly that.
What each requirement can carry
A requirement can record its category, a regulatory reference, whether it is mandatory, a task-card reference, and whether it needs a qualified inspector. That is what makes the due-list an audit answer rather than a reminder list.
How it reaches the day
Once a programme is on an aircraft, its requirements appear in the due-list grouped by aircraft, binding item first, with the latest date the aircraft can still be booked before the item lands. A requirement that comes due grounds the aircraft in the calendar automatically.