Flight & Duty Time Limitations · exceptions only
FDTL Compliance Check
Roster-planned and actual duty monitoring against the selected FDTL scheme. Only Breach and At Risk cases are shown.
Last data sync
01 JAN 70 · 06:22Z
Prototype: illustrative rules and dummy data. All limits must be validated against the operator's currently approved FDTL scheme and applicable DGCA directions before operational use.
JAN 1970
Rule basis: Operator approved scheme — OM-A Ch.7 v4.2 · OM-A Ch.7 v4.2 · effective 2026-04-01. Night, WOCL and local-night calculations use each crew member's acclimatised time zone; times displayed with zone.
Exception categories
breach · at riskCumulative limits — exceptions
usage · limit · forecastBreach · 1
At Risk · 9
FDT-2343BreachnewActual
F8 · Extensions & Extension Rest · FDP extension record
Extension record non-compliant — commander's consent not recorded
Actual
1.0 h
Limit
1.0 h
Margin
at limit
Time window
Extension on 30 DEC 69 · report due 07 JAN 70
Calc time zone
IST (acclimatised)
Next scheduled duty
02 JAN 70 06:00 IST · 6E238 / 6E241
Forecast to breach
No
Owner
Unassigned
Last updated
31 DEC 69 · 21:30Z
Rule basis
Extensions for unforeseen circumstances require commander's consent, a stated reason, a discretion report within 7 days, and are limited to 1.0 h (FDP) / 1.0 h (flight time).
Source rule
OM-A 7.8 (Commander's discretion)
Scheme
OM-A v4.2 (approved)
Rule version
OM-A Ch.7 v4.2
Effective
2026-04-01
Type / amount
FDP +1.0 h (allowance 1.0 h)
Reason
Weather holding BOM, ATC flow control
Commander's consent
NOT RECORDED
Discretion report
not filed · due 07 JAN 70 06:15 IST
- Required elements: consent, reason, report, amount ≤ allowance.
- Missing / non-compliant: commander's consent not recorded.
Rule OM-A 7.8 (Commander's discretion)Version RV-OPS-4.2Mode actualSources 2
Actions
New → Acknowledged → Actioned → Resolved
Audit history
- createdFDTL Rule Engine31 DEC 69 · 21:30Z
Raised — Extension record non-compliant — commander's consent not recorded
rule OM-A Ch.7 v4.2