Flight department software cost comes from two places: the subscription, which vendors price per aircraft, per user, per module or by some mix of the three, and the one-time costs of getting started, such as setup, data migration and training. The subscription is the number on the quote. The one-time fees, plus the staff hours it takes to load your data and learn a new system, can add up to more than the first year’s subscription, and the staff hours never appear on a quote. To compare offers fairly, add both over the full contract term and set them against what your current spreadsheets and paper already cost you in time.
This post doesn’t quote any vendor’s prices or market ranges, because prices change and depend on your fleet and contract. Any number below is illustrative, round on purpose so the arithmetic is easy to follow. Put your own quotes and your own staff hours in its place.
How is flight department software priced?
Quotes are built from a handful of pricing units. Knowing which one a vendor uses tells you how the bill will grow as your operation changes.
| Pricing unit | What you pay for | What makes the bill grow | Ask the vendor |
|---|---|---|---|
| Per aircraft | Each aircraft in the system, usually per month | Adding aircraft | Is a parked or sold aircraft still billed? What about one added mid-period? |
| Per user (seat) | Each person with a login | Hiring, adding contractors, giving mechanics or schedulers access | Do read-only users count? Do contract pilots? |
| Per module | Each functional area: scheduling, maintenance, crew, accounting, portal | Turning on more of the product | Which modules do I need for my operation type? Are any required? |
| Tiered by operation | A plan that matches Part 91, Part 135 or Part 91K work | Adding a certificate or program | What changes if we add charter work later? |
| Flat fee | One price for the company | Usually nothing until a size cap | Where is the cap, and what happens past it? |
A quote can combine two units: a plan chosen by operation type and priced per aircraft, say, or a base fee plus a charge per user. The structure matters more than the headline rate, because it decides what you’ll pay in year three, after the fleet or the team has changed.
If you’re still deciding what the software has to do, start with our guide to flight department software. Pricing only makes sense once you know which functions you need.
Per aircraft or per user: which costs less?
It depends on the ratio of people to aircraft in your operation. A flight department usually has far more people who need access than it has aircraft: pilots, schedulers, a director of maintenance, mechanics, an assistant who books hotels, someone in finance who approves expenses. Charter operators add salespeople and dispatchers.
Here is how the number of billed units changes for three illustrative operations. These are made-up shapes, not real customers:
| Illustrative operation | Aircraft | People who need a login | Units billed per aircraft | Units billed per user |
|---|---|---|---|---|
| Single-aircraft corporate department | 1 | 6 | 1 | 6 |
| Three-aircraft department with in-house maintenance | 3 | 18 | 3 | 18 |
| Five-aircraft charter operator with a sales desk | 5 | 30 | 5 | 30 |
A per-user rate and a per-aircraft rate aren’t comparable unit for unit, so the table doesn’t settle which is cheaper. What it shows is how each one moves. Under per-user pricing, each new hire or contract pilot raises the bill, which can push departments to share logins or keep people out of the system. Both undermine the reason you bought it: a shared login means you can’t tell who changed a trip, and a mechanic without access means defects get reported by text message again. Under per-aircraft pricing, the bill tracks the fleet, which is usually what the budget is built around anyway.
To compare two quotes with different units, convert both to a yearly total for your real headcount and fleet, then do it again for the fleet and headcount you expect in two years.
What one-time fees should you expect?
The subscription is a recurring cost. There are also costs you pay once. Some are fees on the quote; some are your own staff’s time.
Setup and onboarding fees
Some vendors charge to configure the system for you: your aircraft, your users and their roles, your duty policy, your risk questions. Others leave that to you with help articles and a support inbox. Ask what the fee covers in hours or deliverables, and what happens if setup runs long.
Data migration fees
Moving your existing records in is usually the largest one-time job. For a flight department, that means aircraft and their counters (hours, cycles, landings), maintenance items and when each comes due, crew certificates and training records, passenger travel documents, and sometimes open trips. Vendors price this several ways: a fixed fee, a fee per aircraft, hourly, or included. Ask exactly what they’ll load, from what format, and who checks it.
Maintenance data deserves extra care, because the records it comes from are required by regulation. Under 14 CFR 91.417(b)(2), the records of total time in service, life-limited parts, overhaul times, inspection status and airworthiness directive status “shall be retained and transferred with the aircraft at the time the aircraft is sold.” A migration that drops a counter or mistypes a due date leaves you with a tracking system that disagrees with the records you’re required to keep. Plan to check every imported item against the logbooks before you rely on the software’s due dates. Our guide to aircraft maintenance tracking covers what each item should carry.
If you load the data yourself, a CSV import makes the job far shorter than typing. In Avion Desk, you can bring your fleet, maintenance items and counters in from CSV, and people, credentials and training the same way.
Training
Someone has to teach the schedulers, pilots and mechanics how to use the new system. Vendors may charge for live training sessions, include a fixed number, or rely on recorded material. Beyond any fee, each person spends hours away from their normal work, covered below.
Annual contract or month to month?
Contract terms change the real cost as much as the price does. Read these before you sign:
- Term length. A multi-year term may carry a lower rate but locks you in if the product doesn’t work out. Ask whether you can try the software on your own data before the term starts.
- Renewal. Does the contract renew on its own? How much notice do you need to give to leave, and can the price rise at renewal?
- Adding aircraft mid-term. Is a new aircraft billed from the day it’s added, from the next month, or at the next renewal? Is it prorated?
- Removing aircraft. If you sell an aircraft, when does it come off the bill, and is anything credited for the rest of the period?
- Minimums. Is there a minimum number of aircraft, users or modules, even if you use fewer?
- Payment timing. Annual in advance, quarterly or monthly. Paying a year up front ties up cash and raises what you lose if you leave early.
- Leaving. Can you export all your data, in a usable format, at no charge? Data you can’t get out is a switching cost you’ll pay later. Our post on switching flight department software covers this from the other side.
The costs buyers miss
These costs rarely show up on a vendor’s quote, and the buyer usually pays them in staff time.
Data entry and cleanup
Even with a migration service, your staff will spend hours finding records, fixing inconsistent spreadsheets and checking what was loaded. Old spreadsheets often hold the same aircraft under two names, a training record with no date, or a maintenance item whose interval was changed in one file and not the other. Every one of these has to be resolved by someone who knows the operation.
Onboarding time for each person
Each user needs time to set up a login, learn the screens they use and get comfortable enough to stop keeping a private spreadsheet on the side. Schedulers and the director of maintenance need the most; a pilot who only checks the schedule and logs flights needs the least.
Running two systems in parallel
Expect to keep the old spreadsheet or whiteboard going for a few weeks until you trust the new system. That’s sensible, especially for maintenance due dates, but it means every trip and every sign-off is entered twice for that period.
Integrations and workarounds
If the software doesn’t connect to something you rely on, someone copies data between the two by hand. Count those minutes per week as an ongoing cost, not a setup cost.
A worked example of first-year staff time
Every figure in this example is illustrative. Replace the hours with your own estimates and the hourly cost with your own loaded staff cost.
| Task | Who | Illustrative hours |
|---|---|---|
| Gather and clean existing records | Director of maintenance, scheduler | 24 |
| Check imported maintenance items against the logbooks | Director of maintenance | 16 |
| Set up users, roles and policies | Chief pilot, scheduler | 8 |
| Training: 10 people at 2 hours each | Everyone | 20 |
| Parallel running: 15 minutes a day for 20 working days | Scheduler | 5 |
| Total | 73 |
At an illustrative loaded cost of $60 an hour, that’s 73 × $60 = $4,380 of staff time in the first year, before any fee on the quote. Run the same sum for your own operation. If it comes out close to a year of subscription, the vendor whose onboarding saves you the most hours may be cheaper than the one with the lowest rate.
What does staying on spreadsheets cost?
Doing nothing has a price too. It’s paid in hours every week, and in the risk of a missed item. A flight scheduling spreadsheet works until the operation outgrows it; the cost is in the checking and copying around it.
Again, every number here is illustrative. To estimate yours, list the recurring tasks that the spreadsheets force on someone and time them for two weeks:
| Recurring task with spreadsheets | Illustrative minutes per week |
|---|---|
| Copying trip details between the schedule, the trip sheet and the crew calendar | 90 |
| Recalculating maintenance due dates from the latest hours | 60 |
| Checking crew duty and rest by hand for the coming week | 60 |
| Chasing expiring certificates, training and passports | 30 |
| Collecting receipts and rebuilding trip costs | 60 |
| Total | 300 |
300 minutes is 5 hours a week. Over 48 working weeks that’s 240 hours a year. At the same illustrative $60 an hour, it’s 240 × $60 = $14,400 a year of staff time spent keeping spreadsheets in step with each other.
That figure leaves out what spreadsheets cost when they’re wrong: a trip scheduled while an inspection was overdue, a pilot seated after a training event lapsed, a passport found expired at the FBO. You can’t put an honest number on those in advance.
How to compare flight department software quotes
Use the same steps for every vendor, so the totals compare like with like.
- Write down your real numbers. Aircraft today and in two years, and every person who needs a login, including contract pilots and mechanics.
- List the functions you need. Scheduling, maintenance tracking, crew duty and training, passengers, release and risk, accounting, a client portal for charter. Mark which are required now and which can wait.
- Get each quote as a full term total. Subscription for every year of the term, plus every one-time fee: setup, migration, training.
- Price the changes. Ask each vendor what you’d pay if you added one aircraft, sold one, hired three people or added charter operations.
- Estimate your staff hours. Use the worked example above with your own figures. Ask the vendor how long a department your size typically takes to go live, and what they need from you.
- Try it on your own data. A trial or a sandbox loaded with one of your aircraft tells you more than a demo built on the vendor’s sample data.
- Check the exit. Confirm in writing that you can export all your data at no charge if you leave.
A checklist of questions to ask
- What unit do you price by, and what counts as a billable aircraft or user?
- Which features are on which plan, and what changes if we add Part 135 or Part 91K work?
- What does onboarding cost, and what exactly does it include?
- Will you load our data? From what formats? Who checks it?
- When is an aircraft added mid-period billed, and when does a removed one come off?
- Is there a free trial, and are we charged anything during it?
- What happens to the price at renewal?
- How do we get all our data out, and in what format?
Flight department software cost in Avion Desk
Avion Desk is priced per active aircraft per month, with a minimum of one, so adding a scheduler or a contract pilot doesn’t change the bill. An aircraft you add is billed from that day for the rest of the period, unless it goes into a slot you’ve already paid for this period, which costs nothing more; one you deactivate comes off at the renewal, with nothing credited. If you’d rather not load your own records, we can load your data for a one-time fee, charged once per company. There’s a free trial, and nothing is charged during it.
The current figures for each plan, including the plan for charter operators, are on the pricing page. To try it, start a free trial and add one aircraft with its maintenance items to see how your own records look in it, or request a demo. See aircraft and maintenance for what each aircraft’s profile tracks.
Frequently asked questions
How much does flight department software cost?
It varies by vendor, pricing unit and the size of your operation. Compare quotes as a full-term total: the subscription for each year, plus setup, data migration and training fees, plus your own staff hours to get started.
Is per-aircraft or per-user pricing better for a flight department?
A flight department usually has many more people than aircraft, so per-user pricing grows with every hire and can push teams to share logins. Per-aircraft pricing follows the fleet. Convert both to a yearly total for your real fleet and headcount before deciding.
What hidden costs come with flight department software?
The common ones are data entry and cleanup, each person’s onboarding and training time, running the old and new systems in parallel for a few weeks, and manual copying where the software doesn’t connect to a tool you use. Most of these are staff hours, not fees.
Should we pay for data migration?
It depends on how much data you have and how clean it is. If your records are in consistent spreadsheets, a CSV import may be enough. Either way, check every imported maintenance item against the logbooks, because 14 CFR 91.417 requires you to keep those records, and the software’s due dates are only as good as what was loaded.
What should a flight department software contract include?
The term and renewal rules, how adding and removing aircraft or users is billed, any minimums, payment timing, and a written right to export all your data at no charge if you leave.
How do I estimate what our spreadsheets cost us now?
Time the recurring tasks the spreadsheets create, such as copying trip details, recalculating due dates and checking duty by hand, for two weeks. Multiply the weekly hours by your working weeks and your loaded staff cost.
