One schedule, the whole fleet

A timeline grid with your aircraft as columns, booking rules that actually hold, and a dispatch flow that knows the difference between reserved, checked out and back on the ramp.

Right now it's a group text

Somebody asks if the plane's free Saturday. Somebody else already has it, but hasn't said so yet. A third person shows up at the hangar at 8am to find the tow bar still out and the tanks empty from last night's flight. Nobody double-booked it on purpose — there was just never one place everyone actually checked.

A shared whiteboard or a spreadsheet tab works until two people edit it at once, or until someone forgets to cross their block off. And none of that tells you when the plane's actually back — whether it's still out, whether it's overdue, or whether it went down for maintenance and nobody who booked next got a heads-up.

Every aircraft, one timeline

The schedule is a grid: your fleet across the top as columns, time running down the side. See at a glance which plane is free this afternoon without clicking into three separate calendars.

N1234
N5678
N9012

Rules per hangar, location per aircraft

Booking rules — slot size, how long a reservation can run, how many a member can hold, how much lead time — are set once for the hangar. Each aircraft keeps its own timezone, hours of operation, twilight-only flag and home airport, since a two-plane fleet can be based at two different fields.

Booking rules · hangar

  • Slot size 30 min
  • Max length 6 hr
  • Lead time 2 hr

Location · N1234

  • Timezone Central
  • Home field KAUS
  • Hours Sunrise–sunset

Hard conflicts stop cold, soft ones ask first

An overlapping flight is a hard conflict — it can't be booked, full stop, and Postgres' own exclusion constraint backs that up even if two people submit at the same instant. Something like booking outside normal hours is a soft conflict: it's flagged, and a hangar admin can override it when it's a real exception.

Soft conflict

Outside N1234's operating hours

Override as admin

Dispatch: reserved, checked out, completed

A reservation checks straight out into a flight and checks back in when it's done — the same record, not a second system to keep in sync. Reminders go out before a booking, no-shows get marked automatically, and a plane that's checked out and running late escalates to the hangar's admins.

Reserved→Checked out→Completed

N5678 · checked out 1:42pm, due back 4:00pm

Find a time, check the weather, subscribe to the feed

A "Find a Time" helper works around everyone's rules and existing bookings to suggest an open slot. Weather shows up right on the schedule. And every member can subscribe to their own live reservations as a calendar feed that updates itself, no export, no re-download.

Find a time

Sat 9:00–11:30am · N1234 free

KAUS72°F · wind 090@8

What it looks like

A week of reservations across a three-aircraft fleet, timeline grid with aircraft as columns.

Questions people ask before switching

Can two members book the same plane for the same time?
No. A Postgres exclusion constraint stops two live flights from double-booking a plane even under a race — one reservation with a checked-out flight physically blocks the overlapping slot, not just a UI warning.
What happens if a booking breaks a rule, like arriving before the lead-time window?
RampMates tells you which rule it breaks. Hard conflicts (like an overlap) can't be booked at all. Soft conflicts (like outside normal hours) can go through if a hangar admin overrides them.
Does the schedule account for the airport a plane is based at?
Yes. Timezone, hours of operation, twilight-only flying and home airport are set per aircraft, so a fleet based at two different fields shows the right local time and daylight window for each one.
Can I see the schedule without opening RampMates?
Yes. Every member gets a subscribable .ics calendar feed of their own live future reservations across every hangar they're in, so it shows up next to the rest of your calendar. Single reservations can also be downloaded individually.
What if someone doesn't bring the plane back on time?
A background sweep watches checked-out reservations and escalates a late return to the hangar's admins, and marks no-shows automatically.
Can a plane be taken off the schedule for maintenance?
Yes. A maintenance block reserves the plane the same way a flight does, but it's excluded from the overlap constraint on purpose — it can sit over a member's existing reservation as a heads-up rather than an outright conflict.

Put your fleet on one schedule

Free during early access. No card, no seat count — just a hangar.