LIVE · BRIEFING WIRE
FlightLogic Brief Daily aviation wire
← Reddit
● RDT COMM ·tekrin ·July 9, 2026 ·16:05Z

Why do 135 operators successfully get away with "rolling rest" schedules?

Some Part 135 cargo operators continue using "rolling rest" schedules despite the 2013 Masterson Interpretation explicitly prohibiting retroactively assigned rest periods as valid rest. The persistence of this practice appears to stem from indifferent Principals of Operations and pilots' reluctance to report violations due to fears of job loss or FAA certificate action against themselves.
Detailed analysis

The forum discussion raises a persistent enforcement gap in Part 135 operations: the practice of "rolling rest," where operators retroactively designate rest periods after the fact rather than affirmatively scheduling them in advance. This practice runs contrary to the FAA's 2013 Masterson Interpretation, a legal interpretation issued by the FAA's Office of Chief Counsel that established a clear standard—rest periods must be affirmatively assigned before the duty period begins, and a pilot cannot be told after the fact that a given block of time "counted" as rest. The interpretation was meant to close a loophole that on-demand cargo and charter operators had exploited for years, particularly in single-pilot or thin-crew operations where unpredictable duty calls make rigid rest scheduling operationally inconvenient. The original poster's account of an operator explicitly using the phrase "rolling rest" during new-hire indoctrination underscores how normalized this noncompliance has become at some carriers, despite over a decade of regulatory clarity on the issue.

The reasons enforcement fails are structural and cultural, not just a matter of FAA indifference. Part 135 oversight is decentralized through Flight Standards District Offices, and a given operator's Principal Operations Inspector (POI) has enormous discretion over how aggressively to police duty-and-rest compliance, safety culture, and manual adherence. A POI who is under-resourced, inexperienced with a specific segment (like Part 135 cargo feeder operations), or simply disinclined to escalate friction with an operator can allow violations to persist for years without a formal enforcement action ever being triggered. Complicating this further, the FAA's enforcement pipeline typically requires a triggering event—a whistleblower complaint, an accident, an anonymous ASAP or hotline report, or an audit finding—rather than proactive line-checking of duty logs. Pilots are frequently the only ones positioned to generate that triggering event, and the asymmetry of power between an on-call first officer or single-pilot captain and a Part 135 operator with hiring/firing authority creates a strong disincentive to file complaints. The fear articulated in the original post—that speaking up leads to termination or being blamed for "accepting" illegal duty—reflects a well-documented reluctance in the 135 community to use FAA hotline or AC 120-42 style protections, especially at smaller operators without union representation or robust ASAP programs.

This matters significantly for working pilots because duty and rest violations sit at the intersection of fatigue risk management and career risk. Unlike Part 121 carriers, which operate under FAR 117's far more prescriptive flight-and-duty-time rules developed after Colgan 3407, Part 135 operators still largely operate under the older, less protective FAR 135.267/135.269 rest rules, which leaves more room for interpretive gray areas like rolling rest to persist. Cargo operators—especially small-package feeder operations flying overnight schedules for the large integrators—have long been flagged by safety advocates and NTSB as a segment where fatigue-related accidents disproportionately occur, precisely because on-call, irregular, and overnight schedules stress circadian rhythms in ways that scheduled passenger flying does not. Pilots accepting these jobs, often early-career aviators building time toward the airlines, face a real tension between career advancement and asserting regulatory rights, which perpetuates the pattern the original poster describes.

Broader industry trends suggest this issue will remain relevant rather than fade. The pilot shortage cycle of the past several years pushed many low-time pilots into Part 135 cargo and charter flying as a stepping stone, giving operators leverage to maintain marginal practices with a steady pipeline of replacement pilots willing to tolerate them. At the same time, NTSB recommendations following several 135 cargo fatal accidents have repeatedly called for the FAA to extend FAR 117-style fatigue rules to Part 135, a change the agency has been slow to implement via formal rulemaking. Until that regulatory gap closes, enforcement of existing rest requirements will continue to depend heavily on individual POI diligence and pilot willingness to report—both unreliable mechanisms—meaning "rolling rest" and similar retroactive rest-assignment schemes are likely to persist as an open secret in parts of the charter and cargo segment, a reality every 135 pilot should factor into how they vet potential employers and document their own duty times.

Read original article