Multi-location flight operations on one console.
Two fields or ten. Every base is a real record, every airplane has one home base and one current location, and the whole fleet shows up on one map.
- ICAO / FAA identifiers
- Per-base time zones
- Home base vs current location
- Fleet map by base
The moment you added a base, the spreadsheet stopped agreeing with itself.
A base is a record, not a text field.
Each location carries its name, its ICAO or FAA identifier, its address, and its own time zone. Retire a base and it stops appearing without deleting the history attached to it.
One home base per tail. Enforced.
An airplane has exactly one home base and, separately, exactly one current location. Not "usually KJFK" — a single row, so two people can't disagree about where the airplane lives.
The airplane that's away is marked away.
Move a tail to another field for the week and its current location changes while its home base doesn't. Dispatch at the far end sees an airplane; the books still know whose it is.
The whole fleet, by base, on one map.
Aircraft group by base with a marker per field coloured by the fleet's status mix there. One glance tells you which base is short and which base is grounded.
Fleet counts per location, not just per org.
The fleet overview breaks down by location and by aircraft type alongside the org totals — including what's due for an annual or a 100-hour soon.
Bring the bases with the spreadsheet.
The aircraft importer recognises a base column whether your export calls it homebase, base, airport, or location, so a multi-field fleet arrives already assigned.
Bases, not branches.
A base is a location inside one organisation, not a second account. One schedule, one maintenance history, one set of books, whichever field the airplane is sitting on — and security isolation stays at the organisation, so adding a base never means splitting your data in two.
How isolation works- Location recordName, airport identifier, address, time zone, active flag.
- Aircraft assignmentAny number of authorised locations per tail; one home base; one current location.
- Fleet rollupCounts and status by location and by aircraft type, with annuals and 100-hours due.
The capabilities behind every base.
Multi-base and training? Flight schools and flight academies. Shared ownership across two fields? Flying clubs. Moving off another tool? Start with the migration path.
- How many bases can one organisation have?
- There's no cap on locations. Aircraft counts are what the plans limit: up to 10 on Club, unlimited on Academy — spread across as many fields as you operate.
- What's the difference between home base and current location?
- Home base is where an airplane belongs; current location is where it is right now. Each is a single value per aircraft, so a repositioned tail is unambiguous rather than annotated.
- Is the data separated per base?
- No — separation is per organisation, and every base inside it shares one schedule, one maintenance history, and one set of books. That's the point: bases, not silos.
- Can we import a fleet that's already spread over several fields?
- Yes. The importer auto-detects the base column from common header names and assigns each aircraft as it lands, so you aren't reassigning tails by hand afterwards.