A club with 40 members has, conservatively, 200 expiry dates to watch. Licences, medicals, class ratings, type endorsements, instrument currency, and club-specific checkrides — each one a separate clock ticking toward zero. Most clubs manage this with a spreadsheet and a volunteer who also has a day job.
That works until it doesn't.
What Actually Needs Tracking
Before you can build a system, you need a clear list of what goes in it. Clubs often conflate regulatory requirements with their own internal rules, which creates confusion about who's responsible for what.
Regulatory documents — these are legal prerequisites for flight:
- Pilot licence (PPL, LAPL, CPL, ATPL) — no expiry on the licence itself under Part-FCL, but privileges lapse without current ratings and medical
- Medical certificate — Class 2 for PPL, LAPL Medical for LAPL holders; expiry intervals vary by age (Part-MED, Article 4 of Commission Regulation (EU) No 1178/2011)
- Class or type rating — most SEP(land) ratings are valid 24 months (FCL.740.A); revalidation requires either a proficiency check or 12 hours including a training flight with an instructor and a solo cross-country
- Instrument rating (if applicable) — 12-month validity, requires a proficiency check each cycle
- Night rating — no revalidation requirement, but night currency is a separate matter
Club-level documents — these are your internal rules, not EASA's:
- Initial club checkout (aircraft type or variant)
- Annual club proficiency check or biennial flight review equivalent
- Solo cross-country endorsement for student members
- Tailwheel or complex aircraft endorsement if your fleet includes them
That second category is entirely within your authority to define and enforce. Most clubs do. The problem is that enforcement is only as good as the tracking behind it.
Where the System Usually Breaks Down
The spreadsheet-and-volunteer model has a specific failure mode: it's synchronous and manual. Someone has to remember to check it, update it, and act on it. When that person is busy, travelling, or simply burned out, the spreadsheet goes stale.
A member whose medical expired three months ago may not have flagged it to the club. They may not have noticed themselves. They book a slot, the duty instructor sees a familiar name and waves them through, and an aircraft departs with a pilot who has no valid medical. Nobody intended that outcome. It happened because the system required someone to catch it at the right moment.
The operational risk here is real. If an incident occurs and investigation reveals the PIC was flying on an expired medical or lapsed rating, the club's insurance position becomes complicated — and the accountable manager or committee officers may face uncomfortable questions from the CAA or their national aviation authority. This isn't a legal opinion; it's a predictable consequence of operating outside regulatory compliance.
Currency gaps are subtler but arguably more common. SEP revalidation by experience (the 12-hour route under FCL.740.A) requires the pilot to log and present the hours — clubs rarely verify this independently. A member who hasn't flown in 14 months may genuinely believe their rating is current because they completed a cross-country in month 11. Whether they met all the criteria is a different question.
The Documents That Slip Most Often
Based on how clubs typically operate, three documents cause the most problems:
Medical certificates. Pilots are personally responsible for their medical validity, but clubs rarely verify it at booking. A Class 2 medical for a pilot over 40 is valid for 12 months; under 40, it's 60 months for the first certificate and 24 months thereafter (Part-MED.A.045). These intervals are short enough that a member who joined two years ago may already be on their second renewal cycle — and the club has no record of the new certificate.
SEP rating revalidation. The 24-month clock resets from the expiry date, not the revalidation date, if revalidated within the final 3 months of validity. Many members don't understand this. Many clubs don't track it at all, relying on the member to self-declare.
Club checkrides. These are entirely the club's responsibility to track, because no external authority is watching. A member who was checked out on your Cessna 172 four years ago and has since transitioned to flying mostly at another club may return with skills that have drifted — but your records show a completed checkout and nothing more.
Building a System That Doesn't Depend on One Person
The goal is a process that runs without requiring a specific person to remember to run it. That means:
-
Centralised document storage with defined fields. Every member record should have named fields for each document type, the expiry date, and the date the club last verified it. Not a notes column — structured fields that can be queried.
-
Automated expiry alerts. The system should notify both the member and a designated club officer at 90 days, 60 days, and 30 days before expiry. Members renew their own medicals; the club's job is to make sure someone knows when renewal hasn't happened.
-
Booking integration. This is the critical link most clubs miss. If a member's medical is flagged as expired or unverified, their ability to book aircraft should be blocked — or at minimum, a warning should appear that requires acknowledgement. A scheduling system that doesn't know about document status is only doing half the job.
-
Documented verification, not self-declaration. When a member uploads a renewed medical or rating, someone on the committee or ops team should mark it as verified against the original. Self-declaration is fine for initial notification; it shouldn't be the end of the process.
-
Succession-proof records. When your membership secretary leaves after five years, the system should still work. If the knowledge lives in their head or their personal spreadsheet, you have a single point of failure.
Planebooker's member document tracking handles the expiry monitoring and booking-block logic directly. When a document lapses, the member can't book until it's updated and verified. That's not a policy decision you have to enforce manually each time — it's enforced by the system.
A Note on Responsibility
Pilots are legally responsible for their own currency and medical validity under Part-FCL. The club is not their licence authority. But the club is responsible for who it puts in its aircraft, and "we didn't know" is a thin defence if the information was available and the process to capture it didn't exist.
The practical standard to aim for: if an auditor asked to see your currency records for any member who flew in the last 12 months, you should be able to produce them within a few minutes. If that's not currently true, the gap is in your process, not your intentions.
Getting Your Records into Shape
If you're starting from a stale spreadsheet, the recovery process is straightforward but requires a deadline:
- Set a date — 30 days is realistic — by which every active member must submit current copies of their licence, medical, and any ratings.
- Suspend booking privileges for anyone who hasn't complied by that date. This will feel harsh. It's the only thing that actually works.
- Once you have current records, move to a system that maintains them automatically.
- Define your club-specific documents and expiry intervals in writing, so new committee members inherit a clear policy rather than informal practice.
The volunteer who's been holding this together deserves a system that doesn't require heroics to operate. So does the member who assumes someone is watching the dates so they don't have to.