Part 135 · Network-aware scheduling
Crew-base efficiency
Trips are scored against where your crew are actually based, surfacing deadhead legs and out-of-base overnights, so the desk can prefer assignments that begin and end at a crew member's domicile. On the ad-hoc charter side the inputs are trips and positioning rather than fixed lines, but the read is the same. It replaces eyeballing which trips strand a crew away from base.
Launching the first quarter of 2027.
Illustrative — every screen reflects your own data.
What crew-base efficiency gives you
- In development — will score trips against where crew are based
- Surfaces deadhead legs and out-of-base overnights
- Helps position trips to return crew to their domicile
How an operator uses this
As trips are positioned, the board checks whether each tail's next-due maintenance check can reach a station that's both reachable and rated for it before the limit, and surfaces an at-risk chip when it can't — advisory only, so it flags the risk on the board without blocking dispatch. Trips are scored against where crew are actually based, surfacing deadhead legs and out-of-base overnights, and the soft factors roll into one configurable weighted score shown as abstract points where lower is better — you set the weights, and it's a planning signal, not a dollar figure. When a swap or re-base would lower that score without creating a routing risk, the board proposes it and shows the reasoning. These are deterministic, explainable heuristics that compose with the FAR 117 / 121.467 legality the scheduler already enforces — not AI, not a solver, and not a claim of the single optimal schedule.
Illustrative — every screen reflects what's in your own data, nothing more.
Keep exploring
Other features in Part 135
Dispatch board
Trip assignments and ops board across the fleet.
Deep diveTrip-sheet briefing
METAR/TAF, NOTAMs, fuel, and W&B on one printable release page.
Deep diveLive aircraft tracking
FlightAware AeroAPI position + ETA, with token share links (bring your own AeroAPI key).
Deep diveClient accounts
Charter-customer directory with billing and trip history.
Deep diveInvoicing + Stripe Connect
Card and ACH payments routed to the operator's connected account; wire-transfer reconciliation for B2B.
Deep diveCargo & ULD
IATA ULD types, AC 120-85 inspection clock, and hazmat tags for freight ops.
Deep diveEndorsement & recurrent timeline
Per-pilot recurrent training and currency, sorted by the next 60-day cliff.
Deep diveCrew duty board
Live duty/rest status per crew member, derived from shifts and the flight log.
Deep diveFatigue risk board
Deterministic, explainable risk from duty load plus self-reported sleep — not AI prediction.
Deep diveMEL — minimum equipment list
Category A/B/C/D deferrals with auto-rolling expiry; expired items ground the aircraft.
Deep diveTime-limited POI access
Read-only Ops Spec review access that expires automatically.
Deep divePilot dashboard
Charter pilots: their trips and duty standing, report-for-duty check-in, 61.51 logbook, and currency/credential alerts.
Deep diveDispatch & ops
The live ops / dispatch board, trip sheets, and fleet tracking for the people moving the airplanes.
Deep diveManager & billing
Clients, charter quotes, invoicing, and an audit-ready compliance trail — the run-the-business layer.
Deep diveMaintenance-station routing
Flags when a tail's due check won't reach a capable station before its limit. Advisory — it surfaces the risk, it doesn't block dispatch.
Deep diveWeighted efficiency score
A configurable weighted score (abstract points, lower = better) over deadhead, overnights, repositioning, and maintenance-fit slack — set your own weights.
Deep diveExplainable swap / re-base suggestions
Deterministic aircraft-swap and re-base proposals that improve the score — every suggestion shows its reasoning. Not AI, not a guaranteed optimum.
Deep diveEvery Part 135 workspace also includes the platform-wide backbone — logbook, credentials, compliance, reporting, and audit trail.
See the backboneSee crew-base efficiency on your operation.
It's part of the in-development layer for Part 135, landing Q1 2027 — join the waitlist to get on it first.