What it runs
Twenty-odd modules, and none of them a spreadsheet.
This is the whole surface of a training and FBO operation, in the order a school actually meets it — from the board in the morning to the leaseback statement at the end of the month.
Flight operations
Daily dashboard
What today looks like before anyone asks: flights out, students active, aircraft available, accounts receivable, and anything overdue in maintenance or sitting open as a squawk.
Today's schedule exports straight from here.
Schedule board
The whole day at a glance, with a row for each aircraft, instructor, simulator and room. A lesson that needs a plane, a CFI and a briefing room is one booking, not three — and a double-booking is caught the moment you try to save it.
Zoom and pan, auto-fit to the working day, 24-hour clock throughout.
Dispatch & check-in
Hand the aircraft over, then close it out. Check-in takes hobbs and tach with the logbook detail beside them — day, night, actual and simulated instrument, landings, approaches — prices the flight from that customer's rates, and produces the receipt — all in one step.
One booking can hold several flights: a day block flown as three hops closes as three.
Customers
Students and renters: certificates, medical, ratings, IACRA FTN, TSA and citizenship status, assigned instructor, running balance, comments, and their own logbook.
Papers and currency raise advisory warnings at dispatch, never a hard block.
Fleet
Aircraft & instructors
Rates, meters, utilisation, maintenance items and open squawks per aircraft. Instructors sit in the same register because they are scheduled the same way — with their own pay rates for dual and solo supervision, kept away from anything a customer sees.
Maintenance
One fleet-wide view of what is due, due soon and overdue, against both hour and calendar intervals, plus every open squawk. The same calculation drives the badge on the dashboard, the aircraft page and the dispatch warning, so they can never disagree.
Fuel
Tanks with running volume, deliveries in, transfers between tanks, sump tests and fuel sales out.
Leasebacks
Owner and aircraft revenue splits, with monthly statements you can hand to the owner.
Billing
Receipts & payments
Receipts carry generated lines for flight and instruction time and any manual lines you add. Editing the flight regenerates the automatic ones and leaves yours alone. Payments can be split across methods.
Draft → open → paid or void. Drafts stay out of every balance and revenue figure.
Block time
Prepaid block-hour contracts that draw down as the hours are flown, so the balance on the account is the balance in the air.
Gift certificates
Issue, search, redeem and void — including redemption against a discovery flight booked through the site.
Reports
Revenue by category, aircraft utilisation, flight activity, A/R aging and instructor pay. Every one of them exports.
Records & compliance
Pilot logbook
Flights flown through dispatch merge with manually entered history into one logbook per pilot, with the columns a logbook actually has.
Renewals
Medicals, flight reviews, registrations and anything else with a date on it, tracked against the person or aircraft it belongs to, with a reminder ladder as the date approaches.
Documents
Keep the documents your operation runs on in one place, track who still has to read what, and print ID badges with a QR code.
Only people signed in to your organisation can open a file.
Safety (SMS)
Hazard, incident and accident reports with risk assessment and the mitigation that followed — the safety register a school is expected to keep, rather than a folder of emails.
Time clock
Staff clock in and out, with hours totalled for payroll.
Booking & portal
Booking from your website
Discovery and scenic flights, charter estimates, standby and waitlist, and observation ride-alongs. Someone booking a discovery flight is added to your prospect list on the way through.
Prospects
Leads captured from the booking flows, ready to convert into a customer when they come back for lesson two.
Customer portal
A separate front door for customers: book their own flights, see their reservations, read their logbook, check their account and update their profile — scoped so they can only ever see their own records.
Customers land here automatically and never see the back office.
Admin
Organisation settings
Name, timezone, currency, and the switches that decide what the forms ask for — whether instruction time is recorded separately, whether fuel added goes on the check-in.
Staff & access
Staff accounts and what each of them can reach, plus the rates every aircraft and instructor charges to each type of customer.
Which notifications go out, from which address, and the log of everything that was sent. Off until you turn it on, and silent about everything that existed before you did.
Status board & deletion log
Announcements that appear on the portal home, and a record of what was deleted, by whom, and when.
Access
Six levels, and people only see their own.
A dispatcher never opens a billing screen that then refuses to save. If somebody cannot use a part of the system, it is not in their menu at all.
Customer
Their own bookings, logbook and account, in the portal only
Staff
The office side of things, mostly to look at
Dispatcher
Dispatch, check-in and the day's board
Instructor
Their students, their schedule, their logbook entries
Manager
Billing, reports and the admin section
Admin
Everything, including staff and organisation settings
How it runs
You fly. We keep it running.
Setup, updates and backups are handled. Nothing to install, nothing to keep patched, and no server for anyone at the school to look after.
Nothing to install
No server to buy, no software to update, no one to call when it needs patching. It opens in a browser, on the desk computer and on a phone at the tie-downs.
Everything exports
Every list on every page downloads as Excel, CSV or PDF, filtered exactly the way you were looking at it. Your accountant gets a spreadsheet, not a screenshot.
Email never holds up the desk
Confirmations and receipts go out after the work is saved, never during it. A slow email provider can delay a message; it can never delay a dispatch or leave somebody waiting at the counter.
One school or several
A group running more than one school can keep them together with separate books, or keep them completely apart. Either way the figures never mix.
See it with your own fleet on it.
Bringing your history across can be done as many times as you like, so the first look can be at your own aircraft and your own students — not someone’s sample school.