oro-ftl

name: oro-ftl description: > Complete EU Regulation 965/2012 Subpart ORO.FTL and CS FTL.1 — all FDP tables (acclimatised, unknown, with FRM), extensions (in-flight rest, split duty, planned), augmented crew, rest facility classes 1/2/3, cumulative flight time and duty limits, rest periods (home base, away, reduced, extended recovery), standby (airport/other), reserve, positioning, disruptive schedules, WOCL, acclimatisation, delayed reporting, commander's discretion, FRM. Operator-agnostic — no simplifications. Use for FTL rule implementation, crew scheduling, roster generation, duty/rest validation, FDP calculations, cumulative counters, fatigue compliance. Trigger on: FTL, FDP, TSV, HDV, duty hours, rest periods, WOCL, ORO.FTL, EU-OPS Subpart Q, CS FTL, augmented crew, in-flight rest, split duty, standby, reserve, acclimatisation, margin calculation, crew sizing.

ORO.FTL — Flight Time Limitations

Complete regulatory framework from EU Regulation 965/2012, Annex III, Subpart FTL and CS FTL.1 (Certification Specifications for Scheduled and Charter Operations), as amended by Regulation 83/2014.

This skill is operator-agnostic — it contains all provisions of the regulation without any simplifications tied to a specific operator, aircraft type, network, or crew configuration.

Regulatory Hierarchy

EU Regulation 965/2012, Annex III
└── Subpart FTL (ORO.FTL.100 – ORO.FTL.250)     ← Implementing Rules (IR), binding
    └── CS FTL.1 (CS FTL.1.100 – CS FTL.1.235)   ← Certification Specifications, default compliance
        └── AMC / GM                               ← Acceptable Means of Compliance / Guidance Material

Operators must comply with ORO.FTL and apply CS FTL.1 as the default means of compliance. Deviations from CS FTL.1 require prior competent authority approval under Article 22(2) of Regulation 216/2008, including FRM-based justification and data collection.

Document Structure

• SKILL.md (this file): Overview, key rules, quick-reference tables, implementation guidance
• references/regulations.md: Complete article-by-article regulatory text with all tables, all CS FTL.1 provisions, and guidance material summaries

When to read the reference file:

• Implementing FDP max lookup → read Section 3 (FDP tables — Table 2, 3, 4, extension tables)
• Implementing in-flight rest logic → read Section 4 (augmented crew, rest facilities, cabin crew)
• Implementing standby/reserve → read Section 8 and 9 (complex FDP reduction rules)
• Implementing rest calculations → read Section 10 (reduced rest, rotation rest, disruptive schedules)
• Implementing acclimatisation → read Section 2 (Table 1, state determination)
• Need the delayed reporting algorithm → read Section 5

Key Definitions (ORO.FTL.105)

Cumulative Limits (ORO.FTL.210)

Flight Time Limits

Duty Period Limits

Post-flight duty counts as duty period. Operator specifies minimum post-flight duty time in OM.

FDP — Quick Reference (ORO.FTL.205)

Basic Maximum FDP (Table 2 — Acclimatised Crew)

Unknown State of Acclimatisation (Table 3 — no FRM / Table 4 — with FRM)

FDP Extension Summary (Mutually Exclusive)

Critical rule: Extension methods are mutually exclusive — you cannot combine in-flight rest with split duty or with planned FDP extension without in-flight rest in the same FDP.

Rest Periods — Quick Reference (ORO.FTL.235)

Standby & Reserve — Quick Reference

Airport Standby (CS FTL.1.225(a))

• Counts in full as duty for ORO.FTL.210 and ORO.FTL.235
• If FDP assigned during ASB: FDP counts from FDP start; max FDP reduced by ASB time >4h
• Max combined ASB + FDP = 16 hours

Other Standby / Home Standby (CS FTL.1.225(b))

• Max duration: 16 hours
• Combination standby + FDP ≤ 18 hours awake time
• 25% of time counts as duty for ORO.FTL.210
• FDP impact: ceases ≤6h → full FDP from reporting; ceases >6h → FDP reduced by excess over 6h
• If FDP extended (in-flight rest or split duty): 6h threshold becomes 8h
• Night standby (23:00–07:00): time between 23:00–07:00 excluded from FDP reduction until contacted

Reserve (ORO.FTL.230, CS FTL.1.230)

• Notified ≥10h in advance
• Reserve times do NOT count as duty for ORO.FTL.210 or ORO.FTL.235
• ORO.FTL.235(d) extended recovery rest applies to crew on reserve
• Max consecutive reserve days specified in flight time specification scheme

Acclimatisation State (ORO.FTL.105, Table 1)

• B = acclimatised to departure time zone → use Table 2
• D = acclimatised to destination → use Table 2 with destination reference time
• X = unknown state → use Table 3 (or Table 4 if FRM implemented)

Implementation Decision Tree

1. Determine acclimatisation state (Table 1)
   ├── B or D → Use Table 2 with appropriate reference time
   └── X → Use Table 3 (or Table 4 with FRM)

2. Look up basic max FDP (reference time × sector count)

3. Apply applicable extension (only ONE):
   ├── In-flight rest? → CS FTL.1.205(c) tables (requires augmented crew)
   ├── Split duty? → +50% of break (≥3h, cap at 6h, exclude WOCL)
   ├── Planned extension? → CS FTL.1.205(b) table (+1h, ≤2× per 7 days)
   └── None → basic max FDP applies

4. Check night duty provisions (CS FTL.1.205(a))
   └── Consecutive night duties: max 4 sectors per duty

5. Apply standby impact if applicable
   ├── Airport standby: reduce FDP by ASB time >4h; combined ≤16h
   └── Other standby: reduce FDP by SBY time >6h (or >8h if extended FDP)

6. Validate cumulative limits (ORO.FTL.210)
   ├── Flight time: 100h/28d, 900h/year, 1000h/12 months
   └── Duty: 60h/7d, 110h/14d, 190h/28d

7. Validate rest (ORO.FTL.235)
   ├── Minimum rest before FDP
   ├── Extended recovery rest (36h/168h)
   └── Days off (Directive 2000/79/EC)

8. Commander's discretion (unforeseen only, post-reporting)
   ├── Standard crew: +2h max FDP, rest ≥10h
   └── Augmented crew: +3h max FDP, rest ≥10h

Other Provisions

Common Implementation Pitfalls

1. Rolling vs Calendar: The 900h limit is per calendar year (Jan–Dec). The 1000h/12m is rolling by calendar month. All other limits (100h/28d, 60h/7d, etc.) are rolling by day.

2. Duty ≠ FDP: Duty includes ground training, admin, positioning. FDP specifically includes flying. Both have separate cumulative limits. Don't confuse them.

3. Rest ≠ flat 12h: It's max(preceding_duty, 12h) at home base. A 14h duty day requires 14h rest, not 12h. After augmented FDP: max(preceding_duty, 14h).

4. Extensions are mutually exclusive: Never combine in-flight rest + split duty + planned extension in the same FDP.

5. Extended recovery rest ≠ just 36h: Must include 2 local nights (22:00–08:00). 36 hours starting at 10:00 spans only 1 local night → invalid.

6. Standby FDP reduction: The 6h/8h threshold and night exclusion rules are complex. See references/regulations.md Section 8 for the complete algorithm.

7. Acclimatisation matters: For operators with time zone crossings, the reference time for FDP table lookup depends on acclimatisation state, not just local departure time.

8. Cabin crew FDP start: When cabin crew reports earlier than flight crew, FDP starts at cabin crew reporting time but max FDP is based on flight crew reporting time (difference ≤1h).

9. Commander's discretion ≠ planned extension: It applies only to unforeseen circumstances starting at or after reporting. Cannot be planned. Requires crew consultation and reporting.

10. Night duty sector limit: CS FTL.1.205(a)(1) limits consecutive night duties to 4 sectors per duty — this is additional to the FDP table sector-based reduction.