Run several bases. One operator.
KFAY, KRDU, KILM — one tenant, one bill, one set of training records. Each base keeps its own dispatch, maintenance log, and roster. The numbers and the students roll up to the operator.
- Per-base dispatch, maintenance log, and roster.
- Consolidated billing, students, and reports across bases.
- Per-base permissions that cascade with overrides.
- Cross-base aircraft borrowing and aircraft loans.
- Aircraft transfer between bases with full maintenance history intact.
Multi-base schools don’t need three logins.
Most flight-school software treats each location as a separate account. Operators stitch the numbers together at the end of the month by exporting CSVs and hoping nothing slipped.
Multi-Location is the inverse. One tenant. Each base keeps its own ops. The operator sees the whole picture without leaving the dashboard, switching accounts, or paying again for every base.
Per-base permissions cascade from the operator. Cross-base aircraft borrowing is a click, not a phone call. Transfers carry full maintenance history with the airframe.
Each base runs its own shop.
Dispatch, per base.
Every base runs its own dispatch board. KFAY's morning brief stays out of KRDU's queue. Schedules, no-shows, and resource conflicts are scoped to the base running the operation.
Maintenance, per base.
Each base keeps its own maintenance log, squawk queue, and AD/SB tracking. Aircraft hobbs and inspections stay with the airframe, not the airport — so a transfer doesn't lose history.
Roster, per base.
Instructors, dispatchers, and students are assigned to bases. A CFI based at KILM only sees KILM's schedule by default. Cross-base assignments are explicit, not accidental.
The operator sees the whole network.
Billing, rolled up.
One bill for the operator, broken down by base. Per-base revenue is visible without forcing the front office to reconcile three Stripe accounts and a spreadsheet.
Students, one record.
A student who flies out of KFAY today and KRDU next month is one record, one logbook, one training file. Their progress doesn't fragment when they cross a ramp.
Reports, every base.
Fleet utilization, instructor hours, and revenue roll up across every base — or drill into one. Identify the base that's thriving and the one that needs attention from the same dashboard.
Cascade from the operator. Override at the base.
Role-based access is scoped per location. A dispatcher at KFAY can’t edit KRDU’s schedule unless the operator says so. Cross-base permissions are explicit and auditable — not the default.
Borrow across bases. Transfer with history intact.
Loan a 172 from KILM to KRDU for a cross-country without losing the airframe’s squawks or hobbs. Permanent transfers carry the full maintenance log, AD/SB status, and inspection due-dates with the tail number.