FAA Part 135 Crew Duty Time and Rest Requirements Explained
How to interpret duty and rest rules with practical scheduling controls for small charter teams.
Why duty and rest tracking matters
Duty and rest controls are safety controls. Most violations occur when teams rely on memory or disconnected systems across dispatch, payroll, and scheduling.
If the first paragraph here is all you need: accurate duty tracking prevents fatigue risk and certificate risk at the same time.
135.265 for unscheduled operations
135.265 establishes flight time limits and minimum rest boundaries for unscheduled operations. Interpretive details can vary by scenario, so your policy should document assumptions and escalation routes.
Always link schedule planning to current duty totals before quote acceptance.
14 CFR 135.265
Minimum rest requirements
Minimum rest periods must be protected in practice, not only planned in software. Last-minute disruptions and informal duty requests are common hidden erosions of rest quality.
Log rest exceptions and review trends monthly to identify recurrent scheduling pressure points.
Compliance warning
A compliant-looking roster can still hide fatigue if duty events are logged late or inaccurately.
Augmented crew operations
Augmented operations introduce additional planning variables and documentation obligations. Ensure your policies define when augmentation applies and how rest facilities and relief procedures are documented.
Avoid one-size-fits-all templates from airline operations that do not match your mission profile.
Calculating cumulative limits
Cumulative windows such as 24-hour, 30-day, 90-day, and 365-day periods require consistent timestamp handling and retroactive correction logic. Manual spreadsheets break quickly at scale.
Use automated rolling calculations and lock historical records once validated.
Common violations operators commit unknowingly
Typical misses include unrecorded repositioning duty, incorrect timezone normalization, and schedule edits that fail to recalculate cumulative totals. These are process design issues more than individual mistakes.
Connect quote acceptance flows in Navlyt TripDesk with compliance alerts in Navlyt Compliance.
Auto-calculation from trip records
When trip data feeds duty calculations automatically, teams spend less time reconciling and more time managing exceptions. That is the operational maturity target.
To build the full workflow, review charter operator CRM software guidance and activate your trial plan.
Navlyt tracks this automatically
Turn recurring compliance work into automated tasks and evidence trails.
Start Free TrialKey takeaways
- Duty tracking is a safety and compliance control, not administrative overhead.
- Model 135.265 assumptions explicitly in policy and tooling.
- Timezone and cumulative-window logic are frequent hidden failure points.
- Automated trip-to-duty sync reduces violations and manual reconciliation.
Author
Navlyt Editorial Team
Navlyt
Written by the Navlyt team. Guides reference the specific regulations they discuss and are general information, not legal or regulatory advice — confirm requirements for your operation with your FSDO or compliance officer.
Was this helpful?
Stay ahead of regulatory changes
Stay ahead of regulatory changes and compliance deadlines.
Related posts
The Complete Part 135 Compliance Checklist for Charter Operators (2026)
A complete checklist of FAA Part 135 compliance requirements for on-demand charter operators covering training, documentation, aircraft, and crew currency.
FAA Part 135 Crew Training Requirements: What Every Director of Operations Must Know
A plain-English breakdown of FAA Part 135 recurrent training requirements for pilots and crew, including frequency and tracking controls.
Why Generic CRMs Fail Charter Operators (And What to Use Instead)
Why Salesforce and HubSpot often miss charter workflow needs, and what charter operator CRM software must include for quotes, legs, and crew coordination.