Operations
Non-scheduled flights: handling last-minute crew assignments
A last-minute assignment is a time-pressured decision that commits the whole week. The "first available" reflex often consumes the only crew member who could have covered the next trip. The sound method establishes who is genuinely assignable, then chooses by looking at the entire roster.
At a non-scheduled operator, most assignments are decided after the roster is published. That is the operating model doing what it was built to do. The last minute will not go away; it can, however, become a tooled decision rather than a reflex.
What counts as a last-minute assignment?
The term covers three situations that are routinely conflated, even though each needs different handling.
- A new trip: a flight confirmed after roster publication. The crew is picked from those on ON days or on standby.
- A reassignment: an already-crewed trip changes hands after a sick call, an FTL limit about to bite, or positioning that no longer works.
- A modified trip: same crew, but times, stops or aircraft change. This is the most dangerous case, because it does not feel like a decision: someone shifts a line, and the week's compliance flips without anyone noticing.
An operator who handles only the first case well leaks through the other two, and those two produce most of the deviations.
These changes also have a dominant cause, and it is human: in the FL3XX × SkAI Tech Crew Management Benchmark 2026, 77% of the 30 business aviation operators surveyed name human factors (sickness, fatigue, last-minute unavailability) as the leading driver of unplanned changes, ahead of weather and maintenance. Reassignment belongs to the normal flow of the operation; treating it as an exception means improvising several times a week.
Why is "first available" the wrong reflex?
Because availability is a resource shared across time.
Assigning the first free crew member is a local decision: it solves today's trip and ignores the consequences. Every assignment consumes duty time, commits a rest period, moves someone away from base and advances rolling counters. Three effects come up again and again:
- Burning the scarce qualification. The only captain current on the type gets Tuesday's easy trip; on Thursday, the trip that requires that type has nobody.
- Cascading positioning. The fastest-available crew is rarely the crew in the right place. Positioning costs a ticket, duty time, and sometimes the FTL margin that will be missing tomorrow.
- Load concentration. "First available" is almost always the same person, the one who says yes. Over time, that is how a resignation gets written.
Finding a legal solution is the easy part; optimised assignment looks for the best one given the full horizon.
What has to be verified before you say yes?
Six families of checks, run before the commercial commitment rather than after:
| Check | What makes it treacherous |
|---|---|
| Remaining duty and flight time | Rolling windows that reach back into last month |
| Rest required before and after | The following rest can break an assignment already made |
| Qualification and currency | An expiry three days out makes the end of the trip non-compliant |
| Positioning and feasibility | The positioning leg itself consumes duty time |
| Documents and admin | Visa, passport, destination-specific authorisations |
| Existing commitments | Training, recurrent check, approved leave, standby duty |
None of these six can be read off a planning grid. All of them are computed, and the first two also depend on the applicable regime: ORO.FTL or, for air taxi, national rules. That is why the last minute is exactly where spreadsheets give way (see our Excel vs crew scheduling software comparison). This list replaces neither the operations manual nor each operator's own procedure: it sets out what a tool has to be able to compute.
How does optimised assignment work?
An assignment engine works in two stages.
First it eliminates. It computes the set of crew members genuinely assignable to this specific trip, applying all six families of checks above. The result is narrower than the list of people on an ON day: only those who can legally and physically operate this flight remain. We detail that calculation in our article on true crew availability.
Then it chooses. Among the remaining candidates, it keeps the one whose assignment degrades future capacity least, while respecting the objectives you set: load balance across crew members, positioning kept down, preferences honoured, cost. That is what smart flight assignment means: a decision made at the scale of the roster, rather than of the single line being changed.
At SkAI Tech, that logic sits alongside full roster re-generation in 12 minutes on average when the disruption outgrows simple reassignment, and equipped operators report 20% fewer roster deviations. Those results are observed across SkAI Tech deployments in 2025-2026, over a scope of more than 70 aircraft and 900 crew members, and vary with fleet size and operating model.
Making these calls every day? See what SkAI Tech changes for crew schedulers.
What is standby for?
A standby reserve is what lets you say yes without touching the published roster. Badly sized, it is either a pure cost or a fiction.
Three parameters make it usable: a defined response time (home or airport standby), coverage by qualification (a reserve not current on the type covers nothing) and fair rotation of the duty. Sizing comes from history: how many trips landed outside the roster each week, on which aircraft, at what notice.
How do you keep a record of what was decided?
The last minute is also when traceability disappears. An assignment agreed by phone and entered into the system an hour later leaves no evidence of what was checked.
In an inspection or an event review, three things must be reconstructable: who was assigned, on what compliance basis, and what alternatives existed. A tool that logs assignments and their checks turns a recollection into evidence.
FAQ
How long should a last-minute assignment take?
The verification has to fit inside the commercial response window, which means minutes. That is only realistic if assignability is computed automatically; done by hand, you either answer too slowly or answer without having checked everything.
Should you call the crew member before or after accepting the flight?
Technically, assignability is computed without them. In human terms, accepting a flight on the assumption that someone on an OFF day will take it is the fastest route to a conflict. See our article on on-demand flying without burning out your crews.
Does optimised assignment take the decision away from the scheduler?
No. The engine proposes and justifies; the scheduler decides, particularly on what the tool cannot know: personal circumstances, client relationship, operational context.
Can our existing ops system handle this?
The data is there, but the assignability computation and the optimised choice usually are not. That is the role of an API-connected add-on, without replacing the system in place.
Sources
- FL3XX × SkAI Tech (2026, August), Crew Management & Business Aviation Operations 2026 Benchmark Report: first-party data, 30 business aviation operators surveyed (drivers of unplanned changes).
- Regulation (EU) No 965/2012, Annex III, Part-ORO, Subpart FTL: flight and duty time limitations and rest requirements; Article 8(2) for the air taxi derogation to national rules.
- SkAI Tech KPIs (first-party data): average generation time and deviation reduction observed across 2025-2026 deployments, varying with fleet size and operating model.
