Maintenance schedules

Plan due work before it costs a flying day.

KitNDocs helps an operation see repeat maintenance, one-off jobs and usage limits before they become a surprise on a flyable day.

Maintenance schedule

Tandem equipment checks

Version 3 in use

Reserve repack

Repeats every 6 months, with a warning before the due date.

Date due next.

Harness inspection

Repeats by calendar or by use, whichever arrives first.

First limit reached.

Replace worn riser

A one-off job sits beside repeat work until it is closed.

Finish once.

Publishing a new version changes no equipment until a person applies it and accepts the new due dates or readings.

The outcome

One place shows what is due, what is coming, and what has changed.

The schedule holds the rule. Each piece of equipment holds its own next due date, reading and completion history.

Put the work in one place.

Each schedule names the work, how often it repeats, when to warn the team, and whether missed work stops use.

Plan repeat and one-off tasks together.

Repack dates, inspection counts and one-off repairs appear in the same view, so the operator sees what needs attention.

Apply changes deliberately.

A new published version does not silently move existing equipment. A person chooses what changes and confirms the next date or reading.

A normal day

The team sees today's alerts and next month's work.

An operator can set up the schedule once, then keep dates and readings current as equipment is used.

Write the schedule.

Name the work and describe the rule source in plain language for the team that will use it.

Add the tasks.

Set repeat dates, usage limits, warnings and one-off jobs where they apply.

Put equipment on the schedule.

Choose the equipment and confirm the first due date or reading for each task.

Keep usage current.

When a flying day adds use to several pieces of equipment, record the readings in one act and see what moved closer to due.

Examples

Dates, counts and one-off repairs can sit side by side.

Skydiving example

A reserve repack warns before the date.

If the repack becomes overdue, the briefing and equipment record show the missed work before the equipment is used.

Paragliding example

A tandem wing inspection follows use.

After a flying day, readings move the inspection closer to due without turning the remaining flights into a guessed date.

Change control

A new schedule version does not rewrite history.

Published versions protect past and current work. The operator can see which equipment still needs review before moving it.

EquipmentVersionWhat it means
Student harness 04Version 3Current
Passenger harness 07Version 2Review
Tandem wing 12Version 3Current

Where it stops

The operator decides what applies.

The operator still chooses what applies.

Categories can help find equipment. They do not put equipment on a schedule by themselves.

The first due value is confirmed.

KitNDocs can calculate from recorded facts. The operator confirms the saved date or reading.

A schedule is not a release to service.

Schedules make work visible. Certificates and the current record show the service state.

Keep proof ready

Put due work where the team will see it.

See how upcoming work reaches the dashboard, then how evidence and certificates record what happened.