Part 135 · Network-aware scheduling
Maintenance-station routing
For each tail, the board checks whether its next-due maintenance check can reach a station that's both reachable and rated for that check before the limit comes due. When it can't, an at-risk chip surfaces on the routing view so the desk sees it while there's still time to re-route. It is advisory: it flags the risk on the board, it does not block or prevent a dispatch. It composes with — never replaces — the FAR 117 / 121.467 crew legality the scheduler already enforces. It replaces noticing a stranded check after the aircraft is already out of position.
Launching the first quarter of 2027.
Illustrative — every screen reflects your own data.
Who it's for
The crew desk that positions tails and wants a heads-up when a due maintenance check won't reach a capable station in time — advisory only, while there's still time to re-route. (In development.)
What it replaces
Noticing a stranded check after the aircraft is already out of position.
What maintenance-station routing gives you
- In development — will flag a tail's due check that won't reach a capable station in time
- Advisory at-risk chip on the routing view — never blocks dispatch
- Composes with the FAR 117 / 121.467 legality the scheduler already enforces
In development: will flag a stranded check
This capability is in development. As planned, the board will check for each tail whether its next-due maintenance check can reach a station that is both reachable and rated for that check before the limit comes due, and surface an at-risk chip on the routing view when it can't. It is intended to replace noticing a stranded check after the aircraft is already out of position.
- In development — will flag a tail's due check that won't reach a capable station in time
- Advisory at-risk chip on the routing view — never blocks dispatch
Designed as advisory, composes with FAR legality
It is designed to be advisory only — it would flag the risk on the board, never block or prevent a dispatch. As planned it composes with, not replaces, the FAR 117 / 121.467 crew legality the scheduler already enforces today.
- Advisory at-risk chip on the routing view — never blocks dispatch
- Composes with the FAR 117 / 121.467 legality the scheduler already enforces
How an operator uses this
This capability is in development. As planned, the board will check for each tail whether its next-due maintenance check can reach a station that is both reachable and rated for that check before the limit comes due, and surface an at-risk chip on the routing view when it can't. It is designed to be advisory only — it would flag the risk on the board, never block or prevent a dispatch — and to compose with, not replace, the FAR 117 / 121.467 crew legality the scheduler already enforces today.
Illustrative — every screen reflects what's in your own data, nothing more.
How it works
Maintenance-station routing, step by step
In development: the board will read each tail's next-due maintenance check and its limit.
It will check whether a reachable, capable station fits before that limit.
When none fits in the window, an advisory at-risk chip will surface on the routing view.
It is planned as advisory only — it would never block dispatch, and it composes with the FAR 117 / 121.467 legality the scheduler already enforces.
Questions
Maintenance-station routing — frequently asked
Is maintenance-station routing available today?
No — it is in development as part of the network-aware scheduling layer. As planned, it will flag when a tail's due check won't reach a capable station before its limit.
Will it block a dispatch?
No. It is designed to be advisory: it would surface an at-risk chip on the routing view, never block or prevent a dispatch, and it composes with the FAR 117 / 121.467 crew legality the scheduler already enforces.
Keep exploring
Other features in Part 135
Dispatch board
Trip assignments and ops board across the fleet.
Deep diveTrip-sheet briefing
METAR/TAF, NOTAMs, and fuel assembled on one printable release page; pax/cargo weight captured alongside them.
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, an AC 120-85-styled inspection clock (non-mandatory FAA guidance), 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 diveCrew-base efficiency
Surfaces deadhead legs and out-of-base overnights so trips can be positioned to return crew to their domicile.
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 maintenance-station routing 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.