BXI checks every duty against your EASA ORO.FTL scheme — FDP, rest, cumulative duty and block hours, extensions and split duty — and warns before a limit is crossed.
FTL compliance is usually checked at the end of the process, by hand, by people who are already doing three other jobs. The rules are detailed — rolling windows, extensions that cannot be combined, rest that must include two local nights — and an honest mistake becomes a finding.
BXI implements EASA ORO.FTL and CS FTL.1 logic with parameters you configure for your own approved scheme: duty time limit tables, cumulative limits, rest periods, sector reductions, FDP extensions, split duty and warning thresholds.
Warnings appear where decisions are made — on crew assignment, on the Sales Calendar and on the crew's own phone — not in a report read the next morning.
Planners stop doing mental arithmetic on rolling windows. Crew can see exactly where they stand on duty and block hours, and safety gets commander's discretion and fatigue data without chasing paper forms.
The FTL engine runs underneath Crew Scheduling, the Sales Calendar and the OCC Dashboard, and feeds the Reports & Safety module with roster robustness and safety performance indicators.