Illustrative aviation photography

CREW CONTROL & RECOVERY

When the plan changes,
keep the context.

Crew control workflows designed to show how each disruption affects assignments, rest, reserve coverage and crew services.

DAY OF OPERATIONS

One delay.
Several decisions.

A later arrival can affect the next duty, the available rest, reserve coverage and a pickup already assigned to a driver. Flilu’s control scope brings those dependencies into the same change workflow.

Record the event, review affected assignments, compare a separate what-if scenario and repeat the relevant rule checks before publishing. Preserve the reason, approver and exact version throughout.

01

Bring the schedule into focus

Import the flight programme, check it against the source and review each amendment.

02

Build a defensible roster

Match duty coverage with crew qualifications, work history, rest requirements and approved rules.

03

Handle the day as it unfolds

Assess the impact, test an alternative and publish a traceable change.

04

Close the operational loop

Keep crew notices, transport arrangements, actual times and safety actions aligned with the published plan.

Aircraft ready on an airport apron

A SCENARIO IS NOT THE LIVE ROSTER

Test the alternative.
Then make the change.

The planned scenario workspace keeps proposed changes separate from published assignments, supplier requests and crew messages. Before applying an alternative, it must identify any intervening changes and repeat the relevant checks.

Explore the operational modules

CONTROL WORKSTREAMS

From the first event to shift handover.

A change is not complete until the affected people and services are working from the right information.

M08Reserve & standby

Distinguish available reserve crew from crew who are eligible for the required assignment.

Separate reserve and standby categories; notification and call-out history; protected rest and contact periods; coverage and utilisation.

M09Day-of-operations control

Understand the crew consequences of delays, cancellations and replacements.

Planned and actual times; effects on subsequent rest; delayed reporting; commander’s discretion records where applicable; replacement checks and recovery coordination.

M10Scenarios & recovery

Test an alternative before changing the live roster.

Separate what-if scenarios; impact comparison; revalidation before applying changes; detection of updates to the live roster. Automated recovery with multiple planning objectives is a roadmap capability.

M11Issues & shift handover

Give every unresolved operational issue a visible owner and next action.

Record severity, deadlines, evidence and escalation; confirm the transfer of open issues between shifts.

A CLEARER VIEW OF CREW OPERATIONS

Start with the whole picture.

Explore the modules, operational workflows and implementation approach behind Flilu.