CM-04 · Fatigue & Rest Rule Compliance (FAR Part 117)

📊

Process Flow Diagram (BPMN)

📋

L4 Process Steps

Step	Step Name	Role / Swim Lane	System	Input	Output	KPI	Dec?	Exc?
Phase 1 1.1	Pull crew schedule and rest window data	Crew Scheduling Analyst	Jeppesen Crew Management	Published crew roster and pairing assignments	Rest window dataset per crew member for next 72 hours	100% of crew records extracted ≤15 min before duty window opens	N	N
1.2	Validate minimum rest vs FAR 117.25 requirement	Crew Compliance Analyst	Jeppesen Crew Management	Rest window dataset from step 1.1	Rest compliance flag (Pass/Fail) per crew member	Zero crew members assigned with <10-hr rest or <8-hr sleep opportunity; compliance check completed ≥4 hrs before scheduled report time	Y	N
1.3	Escalate non-compliant rest to Crew Scheduling	Crew Compliance Analyst	Jeppesen Crew Management	Fail-flagged crew records from step 1.2	Replacement or re-routing request logged in crew scheduling queue	100% of rest violations resolved ≥2 hrs before report time; zero crew members reporting for duty with open violation	N	Y
Phase 2 2.1	Calculate maximum FDP from Table B/C values	Crew Scheduling Analyst	Jeppesen Crew Management	Report time (local), number of scheduled flight segments, acclimation status	Maximum FDP in hours per FAR 117.13 Table B (unaugmented) or Table C (augmented)	FDP calculation completed ≤5 min per crew pairing; 100% of FDPs within published table limits before sign-out	N	N
2.2	Determine if augmented crew operations apply	Crew Scheduling Analyst	Jeppesen Crew Management	Crew complement (2 vs 3+ pilots), planned in-flight rest facility class	Augmented operations flag and applicable FDP extension allowance	Augmented classification accuracy ≥99.9%; mis-classification rate <1 per quarter	Y	N
2.3	Apply FDP extension if operationally justified	Director of Operations (DO)	Jeppesen Crew Management	Operational need justification, augmented crew flag, crew consent	Approved FDP extension record (max 1-hr, once per calendar day per FAR 117.19)	FDP extensions ≤5% of total monthly pairings; no extension applied without documented crew consent	N	Y
2.4	Authorize FDP and issue pre-departure brief	Crew Scheduling Analyst	Jeppesen Crew Management	Validated FDP, rest compliance records, pairing details	Signed FDP authorization record; crew brief packet distributed	100% of crew departures with FDP authorization on file; brief packet delivered ≥60 min before report time	Y	N
Phase 3 3.1	Monitor real-time duty time against FDP limits	Crew Tracking Specialist	Jeppesen Crew Management	Live ACARS/ADS-B block times, ATC delay feeds, gate departure confirmations	Running FDP counter per crew member updated every 15 minutes	Real-time duty counter latency ≤15 min; alert triggered ≥30 min before projected FDP breach	N	N
3.2	Receive and log crew fatigue self-declaration	Pilot in Command / First Officer	Jeppesen Crew Management	Crew member fatigue declaration via crew portal or ACARS datalink	Fatigue event record with timestamp, flight number, and crew ID	100% of fatigue declarations acknowledged by Crew Tracking within 10 min; zero declarations closed without resolution note	Y	Y
3.3	Coordinate AOC for substitution or flight delay	Airline Operations Center (AOC) Controller	SITA Airport Management System (AMS)	Fatigue declaration or projected FDP breach from steps 3.1–3.2	Replacement crew assignment or delay/cancellation decision logged in AOC system	Replacement crew sourced ≤90 min from declaration for flights with >2 hrs to departure; cancellation rate due to fatigue <0.1% of monthly operations	N	Y
Phase 4 4.1	Calculate 60-hr limit in 168 consecutive hours	Crew Compliance Analyst	Jeppesen Crew Management	Historical flight duty records for prior 168 hours per crew member	Rolling 60-hr utilisation figure per crew member; alert if ≥85% (51 hrs)	Zero crew members exceeding 60-hr limit; alert threshold triggered at 51 hrs to allow scheduling intervention	Y	N
4.2	Calculate 190-hr limit in 672 consecutive hours	Crew Compliance Analyst	Jeppesen Crew Management	Historical flight duty records for prior 672 hours per crew member	Rolling 190-hr utilisation figure; alert if ≥85% (162 hrs)	Zero crew members exceeding 190-hr limit in any 28-day window; alert generated ≥10 days before projected breach	N	N
4.3	Track annual 1,000-hr flight time limit	Crew Planning Manager	Jeppesen Crew Management	Year-to-date flight time log per crew member (block hours)	Annual flight time projection and alert if ≥900 hrs (90% of limit)	Zero crew members exceeding 1,000 flight hours in any calendar year; 90% threshold alert issued ≥45 days before year-end for projected breaches	Y	N
4.4	Remove near-limit crew and notify Crew Planning	Crew Scheduling Analyst	Jeppesen Crew Management	Alert flags from steps 4.1–4.3	Crew member status updated to limit-protected; open pairings returned to scheduling pool	100% of limit-alert crew removed from active schedule within 2 hrs of alert; zero limit violations in FAA audit sample	N	Y
Phase 5 5.1	Aggregate fatigue events in FRMS database	Safety & Compliance Analyst	AWS S3 / Redshift	Fatigue declarations, FDP breaches, near-limit alerts from phases 3–4	Consolidated FRMS event dataset with route, crew base, pairing-type dimensions	FRMS dataset refreshed within 24 hrs of event; 100% of fatigue events linked to pairing and route data	N	N
5.2	Analyse fatigue patterns by route, base, pairing type	Safety & Compliance Analyst	Tableau / Power BI	FRMS event dataset from step 5.1	Monthly FRMS trend report with heat-map by route and crew base	FRMS report issued within 5 business days of month-end; ≥3 pairing types or routes reviewed per cycle	Y	N
5.3	Revise pairings and notify Safety Review Board	Crew Planning Manager	Jeppesen Crew Management	FRMS trend report identifying systemic fatigue risk in specific pairings	Revised pairing set submitted for next bid period; Safety Review Board notification issued	100% of systemic-risk pairings revised within 2 bid periods of identification; recurrence rate of flagged pairing type <20% after revision	N	N
Phase 6 6.1	Generate FAR 117 compliance report for FAA	Director of Regulatory Compliance	AWS S3 / Redshift	Duty records, rest logs, FDP authorizations, fatigue event records for reporting period	FAR Part 117 compliance report (quarterly); violation summary if applicable	Report submitted ≥5 business days before FAA due date; zero data gaps in duty record coverage	Y	N
6.2	File voluntary disclosure or corrective action plan	Director of Regulatory Compliance	FAA DragonWave / ASAP Portal	Identified FAR 117 violations from compliance report	FAA voluntary disclosure (ASAP) submission or corrective action plan on file	100% of identified violations disclosed within 10 business days; corrective action plan implemented within 60 days of disclosure	N	Y

📋

Process Attributes

Identification

Process IDCM-04

L1 DomainCrew Management

L2 ProcessCrew Compliance & Certification

L3 NameFatigue & Rest Rule Compliance (FAR Part 117)

L4 Steps19 across 6 phases

Decision Gates8 (all with iteration loops)

Exceptions6 documented

Swim Lanes (Roles)

Crew Scheduling Analyst

Crew Compliance Analyst

Director of Operations (DO)

Crew Tracking Specialist

Pilot in Command / First Officer

Airline Operations Center (AOC) Controller

Crew Planning Manager

Safety & Compliance Analyst

Director of Regulatory Compliance

Systems & Tools

Jeppesen Crew ManagementSITA Airport Management System (AMS)AWS S3 / RedshiftTableau / Power BIFAA DragonWave / ASAP Portal

Key Performance Indicators

Pull crew schedule and rest window data100% of crew records extracted ≤15 min before duty window opens

Validate minimum rest vs FAR 117.25 requirementZero crew members assigned with <10-hr rest or <8-hr sleep opportunity; compliance check completed ≥4 hrs before scheduled report time

Escalate non-compliant rest to Crew Scheduling100% of rest violations resolved ≥2 hrs before report time; zero crew members reporting for duty with open violation

Calculate maximum FDP from Table B/C valuesFDP calculation completed ≤5 min per crew pairing; 100% of FDPs within published table limits before sign-out

Determine if augmented crew operations applyAugmented classification accuracy ≥99.9%; mis-classification rate <1 per quarter

Apply FDP extension if operationally justifiedFDP extensions ≤5% of total monthly pairings; no extension applied without documented crew consent

Authorize FDP and issue pre-departure brief100% of crew departures with FDP authorization on file; brief packet delivered ≥60 min before report time

Monitor real-time duty time against FDP limitsReal-time duty counter latency ≤15 min; alert triggered ≥30 min before projected FDP breach

Airline-Specific Risks & Pain Points

Roster amendments late in the day can invalidate pre-computed rest windows; Jeppesen batch refresh cycles may lag real-time pairing changes by up to 30 minutes

FAR 117.25 requires rest free from all restraint including deadhead travel; mis-classification of deadhead as rest is a common audit finding and can trigger FAA enforcement action

Replacement pool exhaustion during irregular operations forces cascading re-assignments; lack of real-time hotel check-in data makes actual sleep opportunity difficult to verify

FAR 117 Table B/C values vary by report time window; scheduling systems may default to most permissive bracket if report time is ambiguous, creating compliance risk on early-morning or red-eye pairings

Rest facility class (Class 1/2/3) on the aircraft must match the assumption in the FDP extension; discrepancies between charter configuration and published aircraft spec cause mid-trip compliance gaps

FAR 117.19 limits extension to once per calendar day and requires crew concurrence; pressure from operations control to extend without concurrence is a recurring safety culture risk

Inputs / Outputs

Primary InputPublished crew roster and pairing assignments

Primary OutputFAA voluntary disclosure (ASAP) submission or corrective action plan on file

←PreviousCM-03 · Crew Day-of-Operations Tracking NextCM-05 · Crew Training & Recurrency Management→