What this site covers

Translating FAA Part 117 and EASA Flight Time Limitations into production systems is both a compliance obligation and an engineering challenge. This resource focuses on the gap between regulatory text and executable validation logic: temporal normalization, rolling cumulative limits, rest-period checks, fatigue scoring, and the secure, auditable architecture that ties them together.

Every topic is written for practitioners who ship code. You will find normalized data schemas, timezone-aware Python, asynchronous ingestion pipelines, and the validation guardrails that keep crew pairings legally defensible and operationally resilient — from upstream flight-log parsing all the way to inspection-ready audit logs.

The material is organized into three core areas. Start with the architecture and regulatory mapping — now including side-by-side FAA Part 117 versus EASA FTL scheduling scenarios and a queryable reference layer for the FDP tables, rest minimums, and cumulative caps — then move into the rule engines that evaluate duty time, fatigue, and alerting, and finish with the ingestion layer that feeds them clean, reconciled, validated operational data.

Explore the content

Core Architecture & Regulatory Mapping

Translate FAA Part 117 and EASA FTL into version-controlled schemas, duty-time taxonomies, queryable reference tables, dual-jurisdiction comparisons, and secure, audit-ready access boundaries.

Open section

Duty Time Validation & Rule Engines

Build deterministic rule engines for flight-time math, UTC/DST edge cases, rolling-window rest checks, fatigue scoring, and tuned, tiered alerting.

Open section

Flight Data Ingestion & System Sync

Ingest and reconcile flight logs, ACARS OOOI messages, crew rosters, and schedule data with validated, idempotent, asynchronous Python pipelines.

Open section