EASA Cumulative Limits Tracker

Summer rosters meet 100-block-hours-in-28-days first — peak season stacks sectors until the rolling window fills mid-month; the 60-duty-hours-in-7 fence catches disrupted weeks with deep delays; and the 900-per-calendar-year cap shapes autumn rosters for crews who flew a heavy summer. The duty fences (60/110/190) include standby and ground duties per the scheme, not just flying — which is why this tracker logs duty and block hours separately.

Because joint responsibility is the regulatory design: limits bind the crew member as much as the operator, scheduling systems do err (data entry, delayed-block corrections, mid-month transfers), and the pilot who can show their own rolling numbers wins every version of the conversation — the open-time offer that would bust 28 days, the fatigue call that needs evidence, the interview asking for duty history. Thirty seconds per duty is what the cross-check costs.

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.

A plain CSV with one row per entry and labelled column headers — the most portable format there is. Spreadsheets open it directly, most specialised software can map it on import, and a printed copy is perfectly legible to a human reviewer. Nothing proprietary means your duty record is never trapped here.