One aircraft, one open dispatch
The database enforces a single dispatched flight per aircraft. You cannot hand out the same airplane twice because a second dispatch is rejected, not just discouraged by the UI.
+Dispatch and returnPart of Resyrv
The dispatch desk is where the schedule becomes a flight, the meters become money, and the squawk either gets recorded or gets forgotten. Resyrv makes it one flow instead of a clipboard and three follow-ups.
+What's included
The database enforces a single dispatched flight per aircraft. You cannot hand out the same airplane twice because a second dispatch is rejected, not just discouraged by the UI.
Hobbs and tach are recorded out and back, including a second tach for twins. Attach a photo of the meter face at dispatch and at return, so a disputed hour has a picture attached to it rather than two memories.
When a reading runs backwards, jumps implausibly, or does not line up with the previous flight, Resyrv raises a meter exception rather than quietly billing it. Exceptions land in a queue with notifications, so someone resolves it before it becomes a wrong invoice.
Both phases capture signatures by role, with the statement text snapshotted onto the row so it can never be recomputed after the fact. Signing re-authenticates with the member's PIN (bcrypt hashed, five-strike lockout for fifteen minutes). Signatures are voidable with a recorded reason, never edited in place.
The return flow is where a squawk actually gets reported, so that is where Resyrv asks for it. Squawks attach to the correct tail and feed the maintenance side. Fuel purchases are captured the same way and can flow into fuel reimbursement.
Closing the flight is what generates the charges. The cost engine reads your per-flight-type rules and projects the aircraft line, the instruction line, and any fuel reimbursement into the ledger. Nobody re-keys tach time into a billing app on Monday.
Kiosk mode puts the day's schedule on the FBO television full screen. A live fleet map shows what is out, and overdue alerts flag an aircraft that is past its scheduled return.
+Questions
Dispatch is permission-gated. You can grant it to front-desk staff, to instructors, or to members dispatching themselves, and you can allow some roles to dispatch on behalf of others while restricting the rest to their own flights.
If the reading is inconsistent with the aircraft's history it raises a meter exception rather than billing it. The exception goes into a queue with a notification. If it is caught after the fact, the correction path adjusts the ledger rather than editing history silently.
They capture per-signer sole control through PIN re-authentication, snapshot the exact statement the signer agreed to, and are append-only with recorded voids. That is the shape AC 120-78B asks for. What any given signature means legally depends on your operation and your POI, not on us.
Yes. Self-dispatch is the normal mode for clubs and co-ownerships and works fine for a school that wants it. Give the permission to the roles you trust and leave it off for the rest.
Yes. Dispatch and return are built for a phone at the airplane, which is where the meters actually are. Meter photos come from the camera.
Pricing
Start with a 14-day free trial. No credit card required. Pay monthly or save with an annual plan.
Pricing information is currently unavailable. Start your free trial →
Launch Assist · $499 one-time
Moving from spreadsheets or another system? Add guided setup, import help for aircraft, users, documents, core settings, and a go-live checklist after your trial starts.
Contact salesAll plans include a 14-day free trial. No credit card required. Already a member? Sign in →
Add your aircraft and your rates, then see the schedule, the squawks, and the ledger all work off one record. No card required.