+Solutions
Work orders with parts and labor on them, a clock you can actually bill against, inspections tracked on tach and calendar at once, an AD ledger per tail, and a grounding that removes the aircraft from the calendar instead of leaving a note about it.
What Resyrv does for maintenance
Every maintenance system will hold a next-due date. Far fewer will stop an aircraft from being dispatched once that date passes, and that gap is the whole difference between a record and a control. In Resyrv the maintenance state of a tail is wired directly into the schedule: an overdue inspection, an open safety squawk, or an expired airworthiness document takes the aircraft off the calendar and refuses dispatch until somebody returns it to service.
The rest of it is the day job. Work orders that carry parts, labor, hours, attachments, and a sign-off. A parts catalog that knows what is on the shelf and what has fallen under its reorder line. Reminders that count against tach, Hobbs, and the calendar together. And a cost that lands where your operating agreement already says it should, without anybody retyping it into a spreadsheet at the end of the month.
Open a work order against a tail, assign it, name the outside vendor if the work is going out, and schedule it. Parts and labor go on as separate lines with part number, serial, quantity, and unit cost, so the job totals itself. Photos, quotes, and paperwork attach to the order rather than living in somebody's email.
Start and stop time against the work order as you work it, with a note on each entry. Mis-clocked time gets voided with a reason rather than deleted, so the hours on a job stay auditable after the fact.
Annuals, 100-hours, ELT batteries, transponder and static checks, VOR checks, and any interval you define, tracked against tach, Hobbs, and the calendar at once. The reminder fires on whichever arrives first, with the lead time you set.
Keep the AD and SB ledger for each aircraft with method of compliance, due condition, and completion history. Recurring due math is done for you, and an overdue record can warn on dispatch or ground the aircraft outright. Applicability stays your call and your mechanic's.
A parts catalog with part number, alternate number, serial, quantity on hand, reorder minimum, unit cost, condition, and where it physically lives. Vendors sit alongside it with contacts and addresses, so a reorder does not start with hunting for a phone number.
A grounded aircraft leaves the schedule. Members cannot book it, dispatch refuses it, and it stays that way until somebody with the authority returns it to service. A note nobody reads is not a grounding.
The record is only worth something if it’s written by the person who was actually under the cowling.
Common use cases
One volunteer holds the airworthiness of the whole fleet in their head and their inbox. Work orders, reminders, and the AD ledger move that into a record the next officer can pick up without a handover meeting.
A trainer going out of annual mid-week costs a day of revenue and three rescheduled students. Reminders fire on tach and calendar together, far enough out to book the shop instead of discovering it on a Tuesday.
You maintain aircraft you do not own. Work orders, parts, labor hours, and sign-offs live per tail, and the cost lands on the owners according to rules they already agreed to.
A pilot reports a squawk from a phone at the airplane. It reaches the mechanic, attaches to the work order it becomes, and either grounds the aircraft or does not, according to how it was rated.
An insurer, a buyer, or an inspector asks what happened to this airframe. Work orders, service events, sign-offs, certificate numbers, and attachments are already in one place per tail, with dates.
Six months of completed work orders, totalled by month, per aircraft. Most operations discover their reserve rate has been wrong in one direction or the other since the day they set it.
The mechanic is the second reader of every maintenance product and usually the last one considered. The record Resyrv keeps is the one an IA, an insurer, or a buyer asks for two years later.
See the maintenance feature detail
No, and this is the honest edge of the product. Maintenance cost posts to the owners of the aircraft: split across partners by ownership share, charged to the owner's account, or recorded as an organization expense with any reserve drawn down first. There is no customer invoice, no accounts receivable for third-party work, and no estimate-to-invoice flow. A shop selling labor to walk-in customers needs a shop system for that half.
No. Resyrv is the operational record: the reminders, work orders, sign-offs, and history your team references daily. Logbook entries are still made by your A&P. Resyrv exports maintenance data for reconciliation so the two agree.
Resyrv carries a feed of published FAA airworthiness directives you can search and attach to a tail. What it will not do is decide applicability for you. You and your mechanic say which ADs apply to which aircraft; Resyrv then tracks the due condition, does the recurring math, and enforces it on dispatch if you tell it to.
They are a catalog with a reorder minimum, so you can see what has fallen below the line, and parts pulled onto a work order carry their number, serial, quantity, and cost onto the job total. It is not a full inventory system with automatic depletion and purchase orders. If you run a stockroom as a business, it will feel thin.
Maintenance is permission-gated separately from everything else. A mechanic can be given the maintenance module without any access to member money, and a treasurer can be given the money without the authority to return an aircraft to service. Every action carries an audit trail.
Bring us a tail number and its last annual and we will show you what the record looks like a year from now.
Add your aircraft and your rates, then see the schedule, the squawks, and the ledger all work off one record. No card required.
