Part 135 Charter Operations Software: Quoting Against Real Crew, Maintenance and Aircraft Limits

Why the quote is the whole business and the whole risk

A broker calls at 16:40 asking for a light jet from Teterboro to Naples the following morning, returning two days later. The scheduler has eleven minutes before the broker takes the trip elsewhere. In those eleven minutes she has to establish which aircraft is genuinely available, whether the assigned crew will be legal after the positioning leg, whether the aircraft has an inspection due inside the window, whether the runway and performance work at the destination on a warm morning, what the handling and landing fees will be, whether the owner's agreement permits that route, and what price wins the trip while still making money. Today she checks four systems and asks a mechanic. She quotes a number that is roughly right. Two hours later she discovers the aircraft has a phase inspection due at a number of hours that the positioning leg consumes, and the trip is re-crewed onto a larger aircraft at a loss.

That sequence is the operating reality of charter, and it is why the quoting layer is not a sales tool. It is the point where availability, legality, airworthiness and price have to agree, and every one of those four lives in a different system that was never designed to answer a question inside eleven minutes.

Charter operators typically run FL3XX, Avianis or Leon Software for scheduling and trip management, a maintenance tracking service for status, Avinode for marketplace lead flow, and an accounting package behind it. Those tools are real and several of them are good. What they do not do is hold your commercial logic: your pricing matrices per aircraft and per client type, your owner revenue splits, your positioning policy, your aircraft suitability limits, and the rules your director of operations applies when a trip is marginal.

Problem 1: legality has to be checked before the price is sent, not after

Part 135 flight, duty and rest rules constrain what a crew can accept, and the constraint depends on the actual shape of the day including positioning legs and the report time before the first departure. Crew currency adds another layer: recent experience, required checks and any type or airport specific qualification. In practice most operators check legality after the trip is sold, because checking it during quoting is too slow with the tools available.

Scheduling products do hold duty data and will warn you once a trip is built. That is genuinely useful and it is also the wrong point in the process. By then you have committed a price to a broker, and the only remaining options are to absorb the cost of a larger aircraft, buy a crew hotel and a later departure, or decline and damage the relationship.

What a custom build does: run legality as part of the quote calculation, not as a warning afterwards. The engine constructs the full duty day including positioning, applies your interpretation of the rules and your company limits which are usually tighter than the regulation, and returns either a compliant crew assignment or a specific reason it does not work. Where a trip is only legal with a crew change or an overnight, the cost of that appears in the price rather than in next month's results. This single change is what turns quoting from an estimate into a commitment.

Problem 2: maintenance status is a forecast, not a status

Inspections come due on hours, cycles and calendar, and a trip consumes all three. A quote that does not project the aircraft's position at the end of the trip is a guess. Add component life limits, minimum equipment list items with expiry, and an aircraft on ground event three days out, and the aircraft that was available at quote time is not the aircraft that flies.

Maintenance tracking services hold this data well and were built for the continuing airworthiness team rather than the sales desk, so the answer to whether a proposed trip fits is usually a human reading a report. That works at six aircraft and stops working somewhere around fifteen.

What a custom build does: pull the due list continuously and project it against the trip being quoted, so the engine can say that this aircraft has 41 hours to the next inspection and the trip including positioning consumes 9.2, and flag the trips where the margin is thin enough that the maintenance planner should look. The valuable output is not the block, it is the early warning: an operator that sees a due date colliding with a busy week ten days out can move the inspection rather than cancel a charter.

Problem 3: pricing is your commercial policy and it lives in a spreadsheet

Hourly rates by aircraft, daily minimums, positioning policy, overnight and crew expense assumptions, international handling, catering markup, de-icing, peak day surcharges, broker versus direct client rates, contracted client rate cards, and the federal excise tax on domestic air transportation with its indexed per segment component. Every operator prices differently and every operator changes pricing more often than any vendor release cycle allows.

The scheduling products all include quoting, and it has improved. Where it strains is the operator with genuinely bespoke commercial structures: a fractional programme with occupied hour accounting, an owner whose agreement gives a different split on owner sourced trips, a jet card with banked hours and rules about peak days, or a management agreement where charter revenue net of direct costs is credited to the owner at a formula the owner negotiated personally.

What a custom build does: hold pricing as versioned, testable rules with a clear separation between cost model and price model, so you can see the margin on a trip before you send it and reprice a whole client segment without a support ticket. Every quote records the rule versions used, which matters when an owner queries a statement eight months later and the rate card has changed twice since.

Problem 4: owner and fractional accounting is where trust is lost

For a management operator the monthly owner statement is the relationship. It shows the charter revenue earned on the owner's aircraft, the direct costs allocated, the management fee, the maintenance spend, and the net position. Assembling it usually means exporting trips, matching invoices, allocating fuel and handling by hand, and sending a spreadsheet. Errors in that statement are not accounting errors, they are trust events, and owners who stop trusting statements move aircraft.

What a custom build does: generate the statement from the same records that produced the trip, with every line traceable to a leg, an invoice or a maintenance event, and give the owner a portal where they can see it themselves including their own flying. Fractional structures add occupied hour deduction, exchange rules between share sizes and peak day handling, all of which are arithmetic that should never be done by hand. The build target is that the statement is produced on the second working day with no manual assembly, which also means the operator finally knows its own margin per aircraft in time to act on it.

Problem 5: trip execution is a hundred small tasks and a phone

Once a trip sells, someone books handling at both ends, arranges fuel, files the flight plan, orders catering, arranges ground transport, sends passenger documentation for international trips, checks customs and border requirements, produces the trip sheet and tells the crew. Most of it happens by email and phone, and the crew receives a PDF that is out of date by the time they read it.

What a custom build does: turn the trip into a task set generated from its own characteristics, so an international trip automatically creates the border filing and documentation tasks and a domestic hop does not. Crew see a live trip on a phone rather than a PDF, changes push rather than requiring a call, and the passenger receives a single itinerary that updates. None of this is technically hard. It is high value because it removes the failure mode where the only person who knows the change is the scheduler who made it.

What this costs and how long it takes

Across the 2,000-plus projects Digital Heroes has delivered, here is the honest shape for charter operators. A first release covering the quote engine with live availability, duty legality, maintenance projection and your pricing rules runs $90,000 to $200,000 and ships in 14 to 20 weeks. That is a system the sales desk quotes from on day one. A full platform adding trip execution and task automation, crew and passenger apps, owner and fractional revenue accounting, invoicing with an accounting integration and marketplace connectivity takes the total to $250,000 to $600,000 across 9 to 15 months.

What drives the number up in charter specifically: fractional or jet card programmes, because share accounting and banked hour rules are genuinely intricate and every programme is different. International operations, which bring permits, border filings and customs requirements per country. Integration with a maintenance tracking service, which varies enormously in quality depending on the provider's interface. Owner agreements that each have bespoke commercial terms, since every unique term is a rule to model. And the number of aircraft types, because performance and suitability limits are per type and the data has to be curated.

Build versus buy, and when the products are the right answer

Buy if you operate under about six aircraft with straightforward ownership. FL3XX or Leon will run your scheduling and quoting adequately, Avinode will bring you lead flow, and a build would consume money that is better spent on a second scheduler who can answer the phone at 16:40. We say this to operators regularly.

Buy the scheduler, build the quote engine, is the split that suits many mid sized operators. The trip management and crew rostering side of the packaged products is mature, while the commercial layer is where your differentiation lives. A quote engine that calls out to your scheduler for availability and to your maintenance tracker for status, then applies your own pricing and legality logic, is a smaller and lower risk project than replacing everything.

Build fully when your commercial structures are the business. A fractional programme, a jet card, a managed fleet with fourteen individually negotiated owner agreements, or a mixed operation where charter, owner flying and a fractional pool share the same aircraft, all describe a business whose accounting logic cannot be configured into a product built for simple on demand charter. Also build when quoting speed is costing you trips, which you can measure directly: count the requests where you responded after the trip was already sold elsewhere.

How to choose a developer for charter operations software

Ask them to model a quote on a whiteboard. A team that has done this separates request, itinerary with positioning legs, aircraft assignment, crew duty construction, cost model and price model, and it asks immediately whether legality is evaluated before or after the price is sent. A team that draws bookings and invoices has built a reservation system and does not yet know what a duty day is.

Ask how they handle a rate card change without corrupting historical quotes and owner statements. Versioned pricing rules with each quote pinned to a version is the only acceptable answer, because owner disputes surface months later and the rate card will have moved.

Ask who owns the code and settle it in writing before kickoff. You should own the repository, the cloud accounts and the right to hire another firm. Your pricing logic and owner agreements are commercially sensitive and should never sit in a supplier's environment you cannot control. At Digital Heroes the client owns the code from the first commit, and a developer who resists that is selling you a dependency rather than a system.