We use cookies for analytics (Google Analytics, to understand how visitors use the site) and targeting (Meta, to measure our Facebook and Instagram ads). Necessary cookies cover sign-in and security only. See our privacy policy.
Your browser sends a privacy signal (GPC), so Targeting is off by default. You can still turn it on here if you want - your choice overrides the signal.
We take your privacy seriously. Resyrv stores small amounts of information in your browser - cookies and similar storage - to keep you signed in, keep your account secure, and remember your preferences. Those essentials are the minimum the site needs to work.
The rest is your call. Analytics cookies help us understand which pages are useful and where visitors run into trouble. Targeting cookies let us measure whether our Facebook and Instagram ads are worth running. We do not sell personal information, and declining optional cookies never limits what you can do on Resyrv.
You can change your mind anytime - the Cookie Settings link in the footer reopens this dialog. For the full picture, including how to request a copy or deletion of your data, read our privacy policy.
Flight data
The airplane reports its own hours.
Airbly is a data recorder that lives in the aircraft. It watches the engine, notices when a flight starts and ends, and sends what it saw. Connect it to Resyrv and the engine and tach time from each flight reaches your organization within about a minute of shutdown.
That closes the oldest gap in shared-aircraft billing: the return readings. When a pilot opens Return on a reservation the recorder flew, Hobbs In and Tach In are already filled with the reading the recorder implies, labeled so everyone knows where the number came from. The pilot still confirms or corrects it, and nothing closes on its own. The difference is that the honest pilot no longer has to squint at a panel meter in the dark, and the guessed number no longer becomes the invoice.
Resyrv checks the two numbers against each other. If the pilot enters a reading more than a tenth of an hour off what the recorder reported, it opens a meter exception with both figures side by side, so an admin can accept the pilot's entry or replay the billing with the corrected numbers. And if the recorder reports a flight that no reservation covers, your admins hear about it.
In Airbly, an administrator generates the group API key from group settings. Generate it once - regenerating invalidates the old one.
Paste the key into Organization Settings > Flight Data and connect. Recorder aircraft match to your fleet by tail number, and you can fix any mismatch on the same page.
Resyrv shows a webhook URL on the card. Put it in Airbly's group settings and flights arrive within about a minute of shutdown. Skip it and an hourly check still catches everything up.
No, and that is deliberate. The recorder pre-fills the return readings; a person still reviews and submits the return. Automatic closing would put an unreviewed number on an invoice, which is the problem this integration exists to solve.
Never. Recorder time is added to the reservation's own out readings, so the aircraft's recorded Hobbs and tach stay exactly what your people entered.
The recorder still reports the flight, and Resyrv notifies your admins that a flight arrived with no reservation behind it. You can turn that notification on or off under Notifications.
Not today. This integration covers engine and tach time, the airports the recorder saw, and the checks built on those. Position tracking is not part of it.
Add your aircraft and your rates, then see the schedule, the squawks, and the ledger all work off one record. No card required.