Deep dive · 05 — Part 135
Network-aware scheduling
Position aircraft and crew for trip demand while keeping each tail's maintenance reachable — with a weight-configurable efficiency score.
Launching the first quarter of 2027.
Illustrative — every screen reflects your own data.
What's in Network-aware scheduling
Every capability in this part of the Part 135 workspace.
Maintenance-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.
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.
Crew-base efficiency
Surfaces deadhead legs and out-of-base overnights so trips can be positioned to return crew to their domicile.
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.
Weighted efficiency score
A configurable weighted score (abstract points, lower = better) over deadhead, overnights, repositioning, and maintenance-fit slack — set your own weights.
The board rolls the soft factors — deadhead legs, out-of-base overnights, aircraft repositioning, and maintenance-fit slack — into a single weighted score, shown as abstract points where lower is better. The weights are configurable per center, so you decide what matters most for your operation; the score is a planning signal, not a dollar figure. It replaces comparing schedule options by gut feel.
Explainable 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.
When a swap or re-base would lower the efficiency score without creating a maintenance-routing risk, the board proposes it and shows the reasoning behind it — what it changes and how many points it saves. The suggestions are deterministic and explainable heuristics: the same inputs always produce the same proposals, and each one traces back to its inputs. They are not AI, not a solver, and not a claim of the single optimal schedule — they are ranked, transparent improvements you choose to apply. It replaces rebuilding the schedule by hand to test an idea.
More of the Part 135 workspace
See the rest of the operation
A look at more of the same workspace — every figure reflects your own data.
Keep exploring
Other deep dives in Part 135
See network-aware scheduling on your operation.
It's part of the Part 135 workspace. Request a demo or join the waitlist.