For partnerships

The hobbs log nobody can fudge

Split fuel and flight costs, book Saturday without a group text, and keep the squawk list somewhere every partner can see.

What co-ownership looks like without it

Someone texts the group asking who has the plane Saturday. Nobody's sure who flew it last, or what the hobbs read when they brought it back. A squawk got mentioned once, in passing, and never written down. Fuel got charged to somebody's card three weeks ago and nobody's settled up. When the annual comes due, the logbook is a mix of memory and a paper pad in the glovebox.

None of that is anyone's fault — it's what happens when a shared airplane runs on a group text instead of a system built for it.

Built for a plane a few people fly

A gapless log, by construction

Start hobbs and start tach are computed server-side from the previous flight's ending reading — never typed by whoever's flying. There's no field to fudge and no gap to explain at annual.

Per-pilot cost summaries

Fuel logging with payment methods and receipt photo capture, so each partner's flights and fuel roll up into their own summary — settling up is reading a number, not reconstructing a month.

Scheduling with real conflict rules

A timeline for the aircraft, with booking rules your partnership sets. Hard conflicts are blocked; soft ones are flagged and an admin can override. A subscribable calendar feed keeps everyone's own calendar current.

Squawks that don't get lost in a text thread

Log what's wrong with a photo and an urgency — immediate, by a target hobbs, or whenever it's convenient. Resolving one records who and when, so nothing gets fixed twice or forgotten.

One logbook, however many of you fly it

Questions from partnerships

What stops someone from writing down the wrong hobbs?

Nothing to write down. The start of every flight is computed server-side from the previous flight's ending reading, never typed by whoever's flying — so the log has no gap to argue about and no reading to fudge.

How do we split fuel and other costs?

Fuel gets logged against a payment method, with a photo of the receipt, and each pilot's flights roll up into a per-pilot cost summary — so who owes what is a number on screen, not a spreadsheet someone has to maintain.

How do we book the plane without three people wanting Saturday?

The schedule is a timeline for the aircraft, with booking rules your partnership sets — slot size, how long a booking can run, lead time. Conflicts are flagged as you book; an admin among you can override a soft one.

Do we need a dedicated mechanic in the partnership?

No. Roles are admin, pilot and mechanic, and a mechanic is optional — any partner can log a squawk, and whoever handles maintenance for you can be added with that role if you want them in the loop.

Is this priced per person?

No — pricing is by fleet size, not seats. A two-plane partnership and a ten-person partnership on one plane pay the same tier as long as the aircraft count matches. See /pricing.

Get your partnership off the group text

RampMates is invite-only. Request access and we'll set up your hangar.