Crew scheduling that catches §135.267 violations before they happen.

The 11 rules, all enforced

§135.267 is not one rule — it's a stack of cumulative limits that interact across 24 hours, 7 days, 90 days, and a calendar year. An assignment that's legal in isolation can still be illegal in aggregate, and the only way to know is to compute every rule on every assignment.

• 24-hour flight time limits
• 7-day flight time limits
• Quarterly (3-month) flight time limits
• Annual flight time limits
• Required rest period before duty
• Maximum duty period length
• Minimum rest after duty
• Augmented crew thresholds
• Standby/reserve duty rules
• Look-back rest requirements
• Cumulative duty across operators

Why scheduling matters more than dispatch

When a §135.267 violation happens, the FAA cares about the assignment, not the flight. The scheduling moment is when the legal exposure is created — which is why our engine runs at assignment, not at release. By the time the dispatcher is building a release, the legality decision is already locked in.

The crew calendar shows duty / rest / currency state at a glance, color-coded by legality. Drag-and-drop assignment triggers the legality engine before the assignment is committed. If the assignment would create a violation, the engine cites the exact rule and the violating cumulative window.

Currency tracking, integrated

§135.341 90-day landings, §135.293 knowledge tests, §135.299 line checks — all tracked per pilot per aircraft category and class. 60/30/7-day expiry alerts go to both the chief pilot and the pilot themselves. Dispatch is blocked automatically when currency lapses, and any override requires DOM approval with an audit entry.