Charter operations software for small Part 135 operators: what actually fits a 1–5 aircraft fleet

The charter operations software market was built around the operators who could afford it: 10-aircraft fleets, dedicated dispatch staff, full-time training departments. A single-certificate operator running two or three aircraft looks nothing like that customer — and the enterprise tools reflect it in their pricing, their onboarding requirements, and their feature sets.

The practical question for a 1–5 aircraft Part 135 operator is not which enterprise platform to choose — it is what combination of focused tools produces a defensible compliance record without requiring a software manager to operate it.

What a small operator actually needs

Strip away the features built for large operations — fleet optimization, multi-base scheduling, OCC dashboards, integrated MRO — and the core compliance requirements for a small Part 135 operator are the same as for a large one:

• A crew currency record with expiry tracking for each crew member (medical, training, instrument currency, recurrent check)
• A duty time calculation that checks 135.267 before a trip is accepted
• An aircraft airworthiness and MEL check before dispatch
• A FRAT score before each flight
• A flight release record for each departure
• A hazard report channel and a corrective action register
• Safety meeting records

That is a compliance program. It can run on a spreadsheet and an email address. It can also run on software. The software is better because it produces a more reliable audit trail — but the choice of software should be evaluated against this list, not against a feature matrix designed for a 20-aircraft fleet.

The spreadsheet baseline

Many small Part 135 operators run their compliance programs on spreadsheets, and this is not inherently wrong. A crew currency spreadsheet that is updated after every training event and checked before every trip assignment is a functional compliance tool. Its limitations are:

• It requires discipline to maintain — a spreadsheet that is not updated is worse than no spreadsheet, because it creates false confidence
• It does not automate the duty time calculation — the dispatcher or DO must run the math for every proposed trip
• It does not block a release when a check fails — it only shows the information; acting on it is a manual step
• The audit trail is the spreadsheet itself — which can be edited after the fact, and which does not timestamp individual decisions

The spreadsheet is a starting point, not a destination. The question is what to move to as the operation grows or as compliance scrutiny (from FSDO, from insurance, from clients) increases.

What to avoid: enterprise platforms sized for large fleets

Leon, FOS, and similar enterprise platforms have per-aircraft or per-user pricing that becomes burdensome at small scale. More importantly, their compliance features are configured for large dispatch departments — the interfaces and workflows assume a dedicated dispatcher, not a DO who is also the chief pilot and sometimes the PIC.

The setup cost for these platforms — in time, training, and configuration — often exceeds their value for operators below about 5 aircraft. The compliance coverage is also sometimes weaker than advertised for Part 135 US operations specifically, since these platforms were built primarily for EASA environments.

What fits: focused tools by function

The most practical approach for a small Part 135 operator is a combination of focused tools, each doing one thing well:

Currency and crew records

A dedicated crew management tool — or a well-maintained spreadsheet — for training records, medical expiry, and instrument currency windows. The key requirement: it must be able to answer "is this crew member current for this flight on this date" without manual calculation.

Pre-dispatch compliance gate

A purpose-built tool that runs the 135.267 duty/rest check, the 135.247 and 135.297 currency checks, the MEL review, and the FRAT score against a proposed trip before the release is issued — and logs the result with a timestamp. This is the component most often missing from small operator toolkits, because the enterprise platforms that include it are too large and the currency trackers that small operators use do not include it.

SMS documentation

A hazard reporting channel (an email address or simple form) and a corrective action register (a spreadsheet works at small scale). The documentation requirement is the same regardless of aircraft count; the volume is lower.

The compliance gap most small operators have

The most consistent compliance gap in small Part 135 operations is not currency tracking — most operators have some system for that. It is the pre-dispatch audit trail: the documented record showing that duty time, rest, medical, and training currency were checked for the specific crew members on the specific proposed trip date, before the trip was released.

Without that record, the compliance program exists in the DO's head and in the crew's knowledge of their own currency status. When an FSDO inspector asks to see the pre-dispatch compliance record for last Tuesday's flight, "we check these things before every flight" is not a document.

The tool gap is real and specific: there is no purpose-built, affordable pre-dispatch compliance gate designed for 1–5 aircraft Part 135 operators. Enterprise platforms are too large; currency trackers do not gate the release; scheduling tools show the information but do not block the action. Filling that specific gap — with an automated gate that logs the decision in a tamper-evident record — is what changes the compliance posture from "we do this" to "here is the proof."

What the cost-benefit actually looks like

The cost of a compliance tool is visible. The cost of not having one is invisible until it is not: a certificate action for operating with an expired medical, an insurance claim that the hull policy does not cover because the operation was not compliant at dispatch, or a civil suit where the plaintiff's attorney asks for the pre-departure compliance record and there is not one.

For a small Part 135 operator, the compliance program is not overhead — it is the documented evidence that the certificate was operated correctly. The tool that builds that evidence as a byproduct of normal operations is worth far more than its monthly cost.