Maintenance-station routing

How an operator uses this

As pairings and aircraft routing are built, the board checks each tail's next-due maintenance check against the stations that are both reachable and rated for it, and flags any tail whose check won't fit a capable station before its limit — advisory, so it surfaces the risk on the routing view without blocking a dispatch. Pairings are scored against your crew bases, surfacing deadhead legs and out-of-base overnights so the desk can favor pairings that originate and terminate at a crew member's domicile, and the soft factors roll into one configurable weighted score (abstract points, lower is better) you tune per center. When a swap or re-base would lower that score without creating a routing risk, the board proposes it with its reasoning — 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.