Design
Why RampMates won't let you type the starting hobbs
Letting the pilot enter both ends of a flight is how shared-aircraft logs develop quiet gaps. Here's why the start reading is computed on the server instead.
Every shared-aircraft logbook we’ve seen has the same hole in it, and it’s never anyone’s fault.
Somebody flies on a Tuesday, gets back late, and means to log it. Wednesday the plane goes out again. The Wednesday pilot writes down what the hobbs says when they get in — which is correct for them, and wrong for the log, because Tuesday’s flight never got entered. Now there are 1.4 hours the book doesn’t know about. They aren’t attributed to anyone, nobody paid for them, and the oil interval quietly slipped.
You can’t fix that with discipline. Discipline is what everyone already thought they had.
The start reading isn’t yours to enter
So RampMates doesn’t ask for it. When you log a flight, you enter the ending hobbs and tach. The starting values are computed on the server from the previous flight’s ending readings — or, for the very first flight on an aircraft, from the baseline set when the plane was added.
That one decision has some useful consequences:
The log can’t have a gap. Every flight starts exactly where the last one stopped, by construction. There’s no arithmetic anyone can get wrong and no field anyone can leave blank.
A missed flight is visible instead of invisible. If Tuesday never got logged, Wednesday’s pilot sees a start reading that doesn’t match the panel. That mismatch is a question someone asks out loud — “hey, did anyone fly Tuesday?” — rather than a discrepancy that silently disappears into the total.
Nobody has to be trusted with the denominator. In a partnership, hours are money. When the start of your flight is whatever you say it was, every cost split rests on everyone’s memory and goodwill. When it’s the last person’s ending reading, it rests on the record.
What this costs
It means you can’t log a flight out of order, and you can’t log one you forgot from three weeks ago without dealing with the flights that came after it. We think that’s the right trade — a log you can’t quietly corrupt is worth more than a log that’s easy to backfill.
It also means corrections need an explicit path rather than a quiet edit. That’s deliberate, and it’s the part we’re still building out.
The general principle
Anywhere the software can derive a value instead of asking for it, it should. Asking is an invitation to be wrong, and in a shared airplane, being wrong accumulates.