Most aircraft groups don't dissolve over maintenance costs or hangar fees. They dissolve because one member feels like they're paying equal shares for unequal access, and they're usually right.
The member who books every sunny Saturday three weeks out, the one who cancels Sunday morning because the forecast looks soft, the one who holds a slot all week and releases it Friday afternoon — these patterns create real resentment. And because aircraft groups are social arrangements as much as financial ones, resentment compounds quietly until someone leaves or the group splits.
Good booking rules don't eliminate conflict. They give you a framework to resolve it without making it personal.
Start with the access philosophy, not the rule list
Before you draft a single policy, the group needs to agree on one question: are we optimising for equal time, equal opportunity, or equal access?
Those are different things.
Equal time means everyone flies roughly the same hours per month. Hard to enforce, and it penalises members who travel for work or have seasonal flying patterns.
Equal opportunity means everyone has the same chance to book, under the same rules. The member who plans ahead gets the slot. This is the most defensible model for most groups.
Equal access means the aircraft is genuinely available to any member who wants to fly, not perpetually locked up by the most organised person in the group. This requires active rules around advance booking windows and cancellation behaviour.
Most groups benefit from a hybrid: equal opportunity as the default, with guardrails that prevent any one member from dominating the schedule.
Get this conversation done before you write policy. If two members fundamentally disagree on the philosophy, no rule set will satisfy both of them.
Advance booking windows
The single most impactful rule you'll set is how far in advance a member can book.
A long window (say, 60 days) rewards planners and penalises spontaneous flyers. A short window (48 hours) keeps the schedule fluid but makes trip planning nearly impossible.
A tiered window works well for most groups:
- Any member can book up to 14 days out for a single slot
- Longer trips (multi-day, overnight) require group notification and can be booked up to 30 days out
- Peak periods (bank holidays, summer weekends) may have a separate cap
The specific numbers matter less than the consistency. Whatever you choose, write it down and apply it uniformly. The moment you make an exception for one member, you've created a precedent that's very hard to walk back.
Slot length and consecutive booking limits
If your group has four members and one person books the aircraft every Saturday from 0800–1800, the other three members effectively don't have weekend access. Even if that booking is technically within the rules.
Two rules help here:
First, set a maximum single-booking duration. Four to six hours is common for day use. Longer blocks should require group agreement or a formal overnight/trip booking process.
Second, set a consecutive-day cap. One member shouldn't be able to hold the aircraft for five consecutive days without the group having agreed to it. A reasonable default is no more than three consecutive days without a 48-hour gap before the same member can book again.
These rules feel bureaucratic until the first time someone tries to book the aircraft for a two-week trip to the coast without telling anyone.
Peak period caps
Some days are worth more than others. A summer bank holiday weekend, the first good VFR Saturday after two weeks of IMC — these slots are contested. Your standard booking rules may not be enough.
Options:
- Rotation system for peak dates. Maintain a list of designated peak dates for the year. Rotate first-pick rights among members. Simple, transparent, hard to argue with.
- Half-day caps on peak days. No member books more than a half-day on a peak date unless the rest of the calendar is clear 48 hours before.
- Advance ballot. For a handful of premium dates (Christmas week, August bank holiday), run a simple ballot. Members submit requests; conflicts are resolved by draw.
None of these is perfect. The rotation system disadvantages members who can't use their peak-date pick. The ballot adds admin. Pick the one your group will actually follow.
Cancellation policy
Late cancellations are where groups get bitter fast.
A member who books Saturday and cancels Friday afternoon has effectively blocked that slot from everyone else for the week. If it happens once, it's life. If it's a pattern, it's a problem.
A cancellation policy needs two components: a notice threshold and a consequence.
A workable starting point:
- Cancellations with more than 48 hours' notice: no penalty, slot returns to open pool
- Cancellations within 48 hours: member is recorded. After two within a rolling 90-day period, their advance booking window is temporarily reduced (e.g., from 14 days to 7 days) for the following 60 days
- Same-day cancellations after 0800 local: treated as a short-notice cancellation regardless of reason
Weather is the obvious exception, and it creates the obvious loophole. Be specific about what counts as a weather cancellation: a TAF showing IMC at departure time is a weather cancellation. A marginal forecast that the member decided not to fly is a judgment call, not automatically exempt.
Some groups require a weather cancellation to be logged with the actual METAR or TAF at the time. That sounds heavy-handed until you've had the same member cancel three Saturday mornings in a row citing weather on days when everyone else flew.
The member who books and doesn't fly
This is the most common source of quiet resentment in aircraft groups, and the hardest to address because it doesn't look like a violation.
The pattern: a member books slots regularly, holds them until close to the date, then cancels or no-shows. The aircraft sits. Other members who wanted that slot didn't book because it showed as taken.
If your group tracks booking-to-flight conversion, the pattern becomes visible quickly. If you don't track it, it stays invisible until someone raises it at a group meeting and the accused member feels personally attacked.
Building this into policy rather than leaving it to interpersonal confrontation is worth the upfront awkwardness. A simple rule: if a member's cancellation rate exceeds a threshold (say, 40% of bookings cancelled within 48 hours over a rolling quarter), the group committee reviews their booking privileges for the next quarter. No accusation, no drama — just a mechanical trigger.
Platforms like Planebooker make this easier because the booking history is visible to all members and the data is objective. When the conversation is about a number on a screen rather than someone's memory of events, it stays less personal.
What to put in writing
Your booking policy should be a short document — one or two pages — that every member signs when they join the group. It should cover:
- Advance booking window by booking type
- Maximum single-booking duration
- Consecutive-day cap
- Peak period rules and how peak dates are designated each year
- Cancellation thresholds and consequences
- How disputes are raised and resolved (and who decides)
- How the policy itself gets amended (majority vote? unanimous?)
The amendment process matters. Groups evolve. A rule that made sense with four members may not work with six. Build in an annual review.
A note on enforcement
Policies only work if someone enforces them. In most small groups, that means one person — often whoever was most organised at founding — ends up being the de facto administrator. That's fine, but make it explicit. Assign a rotating scheduling coordinator role if you want to distribute the load.
Automatic enforcement is better than manual enforcement. If your booking system can flag a cancellation rate, apply a booking window restriction automatically, or send a reminder when a slot hasn't been confirmed 24 hours before departure — use those features. Rules that require human intervention to apply are rules that create awkwardness.
For groups using a shared scheduling tool, conflict detection and availability logic can handle a lot of the mechanical enforcement, leaving the human judgment for the edge cases that actually need it.
Before you finalise anything
Run a simple scenario test with your group. Take your draft policy and walk through three real situations:
- Two members want the aircraft on the same Saturday morning. Who gets it, and how?
- A member books a four-day trip six weeks out. Another member wants the aircraft on day three of that trip. What happens?
- A member cancels at 0700 on the morning of a booking, citing a personal commitment. What's recorded, and what happens next?
If your policy gives a clear, agreed answer to all three, you're in reasonable shape. If the group argues about any of them, you have more work to do before the policy is ready to sign.
Get that conversation done now, while everyone still likes each other.