Fatigue Risk Management for Aviation: What the FAA’s Anticipated Part 135 Duty-and-Rest Proposal Signals

Under current Part 135 rules, a pilot can be assigned 10 consecutive hours of rest—and still arrive at the aircraft on fewer than six hours of actual sleep. That gap between legal rest and biological recovery is precisely where fatigue risk lives, and it is the gap the FAA appears poised to address. Fatigue risk management is once again at the center of the regulatory conversation, driven by anticipated rulemaking that could reshape how Part 135 operators schedule, train, and monitor their crews.

Why Fatigue Risk Management in Aviation Is Back in the Regulatory Spotlight

Reports within the aviation industry point to a potential FAA initiative—sometimes referenced as a 2026 NPRM—that would modernize Part 135 duty-and-rest requirements. To be editorially precise: as of this publication, no official FAA fatigue NPRM for Part 135 has been confirmed in the Federal Register. The regulatory direction, however, is increasingly clear. The FAA is under sustained pressure from the NTSB, industry groups, and operational experience to close the gap between Part 135’s legacy rules and the evidence-based fatigue controls that Part 117 brought to Part 121 airlines after the Colgan Air accident.

Why has Part 135 lagged behind? The answer lies in operational diversity. Part 135 duty time rules must account for air ambulance missions launching at 3 a.m., single-pilot cargo runs through multiple time zones, on-demand charter flights with unpredictable schedules, and commuter operations with rapid turnarounds. That complexity has made rulemaking difficult—but it has also made it more urgent. The same operational variety that complicates regulation also multiplies the circadian disruption and cumulative fatigue pilots face.

The anticipated regulatory direction signals a move beyond pure hours-of-service compliance toward data-driven fatigue risk management. This article breaks down what the current rules require, what an FRMS actually entails, where the gaps are, and what operators should do now—before any final regulatory text arrives.

Part 135 Duty-Time and Rest Requirements: Where the Rules Stand Today

Before examining where regulation may be heading, operators need a clear picture of where it stands. The existing framework splits into two tracks: scheduled operations under 14 CFR §135.265 and unscheduled operations under 14 CFR §135.267. Both regulate flight time—not total duty time. That distinction matters more than many operators realize. Preflight planning, post-flight duties, positioning legs, maintenance coordination, and administrative tasks can extend a pilot’s workday well beyond logged flight hours, yet none of those activities count against flight-time limits.

Legal rest is similarly misunderstood. A required rest period is time free from assigned duty. It is not a guarantee of actual sleep obtained.

Scheduled Operations Under §135.265

For scheduled Part 135 operations, 14 CFR §135.265 establishes the following flight-time ceilings:

• 1,200 hours per calendar year
• 120 hours per calendar month
• 34 hours over any seven consecutive days

Rest requirements follow a graduated schedule based on scheduled flight time:

• 9 hours of rest for less than 8 hours of scheduled flight time
• 10 hours of rest for 8 to less than 9 hours of scheduled flight time
• 11 hours of rest for 9 or more hours of scheduled flight time

These caps and rest floors are enforceable minimums. They do not, by themselves, account for circadian disruption from consecutive early-morning report times, sustained night flying, or rapid time-zone changes—all of which are routine in scheduled Part 135 environments.

Unscheduled Operations Under §135.267

Unscheduled operations under 14 CFR §135.267 carry a different structure, reflecting the unpredictable nature of on-demand flying:

• 500 flight hours per calendar quarter
• 10 consecutive hours of rest during the 24-hour period preceding the planned completion of the assignment
• 13 rest periods of at least 24 consecutive hours in each calendar quarter

When a pilot exceeds the applicable daily flight-time limit due to circumstances beyond the operator’s or pilot’s control, post-exceedance rest escalates on a sliding scale:

• 11 consecutive hours of rest for moderate exceedances
• 12 consecutive hours for greater exceedances
• 16 consecutive hours for the most significant exceedances

This sliding-scale logic is notable. The FAA already applies a principle of proportional rest within the existing Part 135 rest requirements framework. A future FRMS-oriented rule could extend this proportionality concept further—tying rest and scheduling controls to measured fatigue indicators rather than fixed hourly thresholds alone.

What Is a Fatigue Risk Management System in Aviation?

A fatigue risk management system (FRMS) is a structured, evidence-based framework for identifying, assessing, mitigating, and monitoring fatigue risk across an aviation operation. It is not a waiver, and it is not permission to schedule pilots beyond safe limits. Understanding this distinction is essential for every Part 135 operator watching the regulatory horizon.

Prescriptive flight-time limitations—the kind that currently govern Part 135—set enforceable boundaries. An FRMS builds on those boundaries by adding fatigue science, operational data collection, risk assessment processes, targeted mitigations, confidential reporting, and continuous review. The system treats fatigue as a hazard to be managed, not merely a threshold to avoid exceeding.

Internationally, this approach is well established. ICAO Annex 6, Part I requires States and operators to manage fatigue through prescriptive limits and, where approved, through an FRMS. ICAO Doc 9966 serves as the principal international guidance document for designing and implementing an FRMS. In Europe, EASA ORO.FTL provisions provide a mature regulatory model that integrates prescriptive limits with operator-specific fatigue-risk controls.

The global regulatory direction is unmistakable: prescriptive limits remain the foundation, but a fatigue risk management system adds the operational intelligence to address risks that fixed numbers cannot anticipate. For Part 135 operators, the question is not whether this approach will arrive in the United States, but when—and how prepared they will be.

What the FAA’s Regulatory Direction Signals for Part 135 Operators

Even without a confirmed FAA Part 135 fatigue NPRM, the anticipated regulatory direction reveals clear areas of focus. Based on known gaps in the current Part 135 framework and international precedent, a future proposal would likely address several persistent fatigue hazards that prescriptive limits alone do not control.

Industry safety professionals widely recognize these areas of concern:

• Consecutive early starts and night operations that erode sleep over multiple duty days
• Reserve and standby policies that keep pilots in a state of partial readiness without counting toward duty time
• Circadian rhythm disruption from irregular schedules and time-zone crossings
• Cumulative fatigue building across a week or quarter, invisible in daily flight-time tracking
• Commuting that compresses actual sleep opportunity within a legal rest period
• Fatigue reporting—or the lack of a non-punitive system for capturing it

A future proposal could move Part 135 closer to a combined model: prescriptive Part 135 duty time limits retained as enforceable minimums, supplemented by operator-specific fatigue-risk controls built on data, reporting, and continuous improvement.

From an operator’s perspective, a key concern is implementation cost and complexity. Small Part 135 companies—some with fewer than ten pilots—may face real challenges in staffing, scheduling software, fatigue reporting infrastructure, and data privacy. These concerns are legitimate and will shape the regulatory conversation. But the direction of travel is clear, and operators who begin building capabilities now will absorb those costs incrementally rather than all at once under a compliance deadline.

Actions Operators Can Take Now

1. Audit current scheduling against total duty-time exposure—not just flight-time limits. Track report times, post-flight obligations, and positioning to see the full fatigue picture.
2. Establish or strengthen a non-punitive fatigue reporting system. If pilots cannot report fatigue without fear of reprisal, you have no data. Without data, you have no system.
3. Review training programs for scenario-based fatigue content. If fatigue training consists only of reciting rest-requirement numbers, it is not preparing crews to recognize and manage operational fatigue.
4. Benchmark your operation against ICAO Doc 9966 FRMS elements. You do not need to implement a full FRMS overnight, but understanding the framework reveals where your gaps are.
5. Subscribe to FAA rulemaking docket updates to track any formal NPRM as soon as it publishes.

Legal Roster vs. Safe Roster: Why Compliance Alone Falls Short

The most dangerous misconception in Part 135 fatigue management is that a legal schedule is automatically a safe schedule. It is not. Part 135 rest requirements define regulatory minimums. They do not measure whether a pilot actually slept.

Consider a common scenario. A pilot receives a 10-hour rest period—fully compliant with 14 CFR §135.267. She commutes 90 minutes from the airport to her home. She eats, showers, handles family responsibilities, and sets an alarm to allow 90 minutes for the return commute. After subtracting three hours of travel, an hour for meals and personal needs, and 20 minutes to fall asleep, her actual sleep opportunity is roughly five and a half hours. She arrives at the aircraft legal. She is not rested.

Now extend the pattern. She flies a week of consecutive early-morning report times—each day individually legal, each day producing six hours or less of actual sleep. By day five, she carries a cumulative sleep debt that no single rest period can erase. Flight time is not duty time. Rest is not sleep. Sleep opportunity is not recovery sleep. These distinctions are where fatigue risk management adds value that prescriptive limits cannot.

Three misconceptions persist among Part 135 operators: that ten hours of rest means ten hours of sleep; that a legal schedule is inherently safe; and that fatigue management is solely the pilot’s responsibility. Each of these beliefs erodes the safety margin that pilot fatigue countermeasures are designed to protect. An FRMS addresses all three by making fatigue a shared operational responsibility, supported by data rather than assumptions.

Building Fatigue Risk Management Into Part 135 Training

Training is where fatigue risk management becomes an operational competency rather than a regulatory abstraction. Effective Part 135 fatigue training goes well beyond reciting rest-requirement numbers. It builds the judgment pilots, dispatchers, and schedulers need to recognize when a legal roster crosses into elevated risk.

A robust fatigue risk management system training curriculum should include:

• Clear definitions distinguishing flight time, duty time, rest, sleep opportunity, and recovery sleep
• Interactive duty/rest calculations using realistic Part 135 scenarios
• Recognition of circadian low points—particularly the window between 2:00 a.m. and 6:00 a.m.—and how consecutive exposure compounds risk
• Effective pilot fatigue countermeasures: strategic napping, controlled caffeine use, light exposure management, and proactive sleep scheduling
• Non-punitive fatigue reporting procedures and simulations
• Dispatcher and scheduler responsibilities when a crewmember reports fatigue
• Scenario-based exercises that present legal-but-risky rosters and ask crews to identify the hazard

E-learning methods amplify this training when designed with operational realism. Branching scenarios involving weather delays and extended duty periods force decision-making under pressure. Short, hazard-focused modules keep attention on one fatigue risk at a time. Knowledge checks that distinguish “legal” from “low risk” reinforce the core lesson. Confidential reporting simulations normalize the act of calling in fatigued. Trend dashboards showing early starts, night operations, and fatigue reports close the feedback loop.

Refresher training should be triggered by operational changes—new routes, seasonal schedule shifts, fleet additions—not only by an annual calendar. Fatigue risk management is a continuous competency, not a checkbox.

CTS offers scenario-based Part 135 training modules designed to address exactly these gaps.

Frequently Asked Questions: Fatigue Risk Management for Part 135

What is a fatigue risk management system in aviation?

A fatigue risk management system (FRMS) in aviation is a structured, data-driven framework for identifying, assessing, mitigating, and continuously monitoring fatigue risk across flight operations. Unlike prescriptive flight-time limits, an FRMS uses operational data, crew reporting, and fatigue science to manage risk that fixed numerical thresholds cannot fully address.

What are the rest requirements for Part 135 pilots?

Under 14 CFR §135.265, scheduled Part 135 pilots receive 9–11 hours of required rest depending on scheduled flight time. Under 14 CFR §135.267, unscheduled operations require 10 consecutive hours of rest in the 24 hours preceding the assignment’s planned completion, plus 13 quarterly 24-hour rest periods.

How does Part 135 duty time differ from flight time?

Part 135 flight-time limits apply only to hours spent operating the aircraft. Duty time encompasses all work-related activities including preflight planning, post-flight duties, positioning, and administrative tasks. A pilot’s total workday can significantly exceed logged flight hours, yet only flight time counts against regulatory limits.

Can a legally compliant Part 135 schedule still create fatigue risk?

Yes. A legal rest period guarantees only time free from assigned duty—not actual sleep obtained. Commuting, personal obligations, and irregular circadian schedules can compress true sleep opportunity well below the hours of required rest. Cumulative sleep debt across multiple legal-but-demanding duty days is a recognized safety risk that prescriptive limits alone cannot prevent.

What does the FAA’s anticipated 2026 Part 135 fatigue proposal mean for operators?

As of publication, no official FAA fatigue NPRM for Part 135 has been confirmed in the Federal Register. The anticipated rulemaking direction points toward evidence-based fatigue risk management requirements—including data-driven scheduling controls, non-punitive reporting systems, and FRMS-aligned training—that build on, rather than replace, existing prescriptive flight-time and rest limits.

Preparing for What’s Next in Part 135 Fatigue Regulation

The significance of the anticipated FAA Part 135 fatigue rulemaking lies less in a confirmed rule text and more in the unmistakable regulatory direction: toward measurable, data-driven fatigue risk management that treats compliance as the floor, not the ceiling. Whether a formal proposal arrives in 2026 or later, the trajectory is set. International standards, operational evidence, and accident history all point the same way.

Operators who begin building FRMS capabilities now—through training, non-punitive reporting systems, and scheduling audits—will be better positioned regardless of the final rule’s timing or specific content. Those who wait for published regulatory text to begin preparing will face compressed timelines, higher costs, and a steeper cultural shift.

Before treating any reported rulemaking as final, verify the proposal through official FAA rulemaking or Federal Register sources. Regulatory preparedness is built on accuracy, not speculation.

One of the most immediate steps an operator can take is ensuring its training program addresses fatigue as an operational competency—not just a regulatory checkbox. Explore CTS’s Part 135 Training to build fatigue risk management into your operation’s training program before the next regulatory shift. Stay ahead of Part 135 regulatory changes—bookmark this page or subscribe for updates when the FAA publishes an official NPRM.