Definition
FRMS arose from the recognition that prescriptive duty/rest limits, however carefully calibrated, cannot capture every operational nuance of fatigue management. A long-haul ultra-long-range operation flying east-then-west across multiple time zones may not be safer under the prescriptive maximum FDP than under a fatigue-modeled alternative tuned to the actual circadian impact. The ICAO framework, codified in Annex 6 Part I and the supporting Doc 9966, defines FRMS as a systematic alternative.
The four core components of an FRMS, mapped to the standard SMS structure: (1) Policy and documentation — the FRMS Manual codifies the operator's commitment, scope, accountabilities, and integration with the broader SMS. (2) Fatigue Risk Management processes — hazard identification specific to fatigue (long-haul time-zone crossings, early-morning report patterns, multiple-leg short-haul days), fatigue risk assessment with bio-mathematical modeling tools (Boeing Alertness Model, FAID, SAFE), risk control measures (rostering rules, in-flight rest practices, sleep-quality interventions). (3) Safety assurance — fatigue performance indicators, fatigue reports from crews, sleep monitoring data from a representative sample, post-flight fatigue surveys, and the integration of this data into safety performance review. (4) Promotion — FRMS-specific training for crews, schedulers, and managers; communication of fatigue-related lessons learned across the organization.
The regulatory mechanics. Under FAA §117.7, an operator may apply for FRMS approval to deviate from specific Part 117 limits — typically not relaxation across the board, but variance from a specific limit (e.g., extended FDP for a specific ULR route) where the FRMS demonstrates equivalent safety. EASA's ORO.FTL.110(c) operates similarly within the EASA framework. Approvals are operator-specific, route-specific, and subject to ongoing performance review.
The technical machinery. Bio-mathematical fatigue models use sleep/wake history, time of day, time on task, prior duty pattern, and individual factors to predict fatigue level (often expressed on a Karolinska Sleepiness Scale 1-9 or as a percentage performance impairment). Operators using FRMS routinely run model predictions for proposed rosters and use the predictions as part of acceptability determination. Crews operating under FRMS rules typically report fatigue events through a structured reporting form, and the operator analyzes patterns to refine the model and the rules.
FRMS does not eliminate prescriptive limits. It permits documented variance for specific operations where the science supports it. Most operators run a hybrid: prescriptive Part 117 / EASA FTL for the bulk of operations, FRMS-approved variance for specific challenging routes or duty patterns.
Why It Matters for Flight Schools
FRMS implementation is a major commitment. The data infrastructure (rosters, sleep monitoring, fatigue reports), the analytical capability (bio-mathematical modeling), and the organizational discipline (using the data to actually adjust rosters when fatigue indicators move) all have to be in place. Operators that announce FRMS to gain regulatory variance without building the infrastructure produce paper FRMSs that the regulator audits and finds inadequate.
For smaller operators (regional airlines, charter operators, large GA fleets running fatigue-prone schedules), FRMS may not justify the implementation cost. The prescriptive Part 117 / EASA FTL framework was designed to handle the majority of operations safely without requiring per-operator scientific analysis. FRMS makes most sense for ultra-long-range, time-zone-crossing operations where the prescriptive rules are the binding constraint and the biological reality is more nuanced.
How Aviatize Handles This
Aviatize's safety management module supports the FRMS data infrastructure: structured fatigue reporting forms (filed by crews after duties), integration with rostering data (the duty pattern that produced each fatigue report), and aggregation into safety performance indicators that feed the Safety Assurance review cycle. The platform doesn't run bio-mathematical models itself but integrates with industry-standard tools (FAID, Boeing Alertness Model) where the operator has licensed them.
For combined ATO + AOC operators, the FRMS data structure spans both training operations and line operations — instructor fatigue from extended ground-school days, line-pilot fatigue from long-haul rotations, and the cross-functional patterns (an instructor who also flies line and is accumulating fatigue across both) become visible in a way that isolated single-function systems cannot deliver.