Skydive Aircraft Maintenance Log

A jump Caravan logs more thermal cycles in a weekend than a charter machine logs in a month: cycle-driven items (hot sections, gear, doors) age at multiples of their hour-based expectations. The tracking implication: jump flying is the highest cycles-per-hour regime in aviation — climb at max power, descend like a brick, repeat eight times a day — and the maintenance clock runs on cycles. A record structured around those realities — cycles beside hours, the operation's specific recurring items, per-aircraft history — predicts failures and budgets honestly where a generic date/work diary just accumulates lines.

Make entry friction near-zero (this log's seven fields take thirty seconds), assign the habit to a role rather than a person ('whoever closes the cowl logs the work'), and review the board on a fixed rhythm — weekly in season. Shared operations decay by skipped entries, not wrong ones; the visible next-due badges and entry counts here make skips conspicuous, which is most of the cure.

Clearing site data deletes locally stored entries — that's the price of a genuinely private, server-free design. Protect yourself with the one-click CSV download before any cleanup, OS reinstall or device change: re-importing history later beats reconstructing it from memory.

Use the Export CSV button below the table: it downloads your full fleet maintenance history as a spreadsheet-ready file. From there you can print a clean copy, archive it with your records folder, or import it into any other system. Exporting monthly is a good habit since the working data lives only in your browser.