EASA FTL Calc
iOS Universel / Utilitaires
EASA OPS Rules for Flight Time Limitations (FTL) are valid since 18.02.2016.
EASA FTL Calc helps you to calculate
- cockpit and cabin limits
- actual and maximum flight duty periods (FDP)
- latest on-block times
- duty periods (DP)
- actual and minimum rest times
- state of acclimatization
- commanders discretion
- disruptive schedules
- required local nights at your home base
- extended recovery rest periods
- cumulative duties for 7/14/28 days
It considers
- standby and airport standby
- extension of cabin FDP due to earlier reporting time
- delayed reporting
- in-flight rest for cockpit and cabin (different rules)
- split duty
- extension
- positioning
- time zone differences
- company minimum rest times
- your home base
- "back to back" operation
You don't have to know time zones
- simply select an airport from the database
- time zone is determined by airport and date
- select only reporting airport of first duty day
- and the resting airport per duty day
- next reporting airport will be your last resting airport
- your home base will be known (preferences)
It's not a flight log
- you don't have to enter every single block time
- no management of block times and their cumulative limits
- however imported flights can be shown for information
Cabin and cockpit limits
- may have different reporting times
- in-flight rest is different
- are calculated independently
Rotations
- are stored automatically
- are shown in an own table
- with FDPs and rest times overview
- for cockpit and cabin
- on iPad in a split view
XML Import
- Rosters of BA only
Roster Buster Import
- direct import
- calendar import
Direct App Import
- MyRoster for crew by Lumabyte
- RosterworX
- NASImport
Calendar Import
Quoi de neuf dans la dernière version ?
This release focuses on design and content updates to improve usability and clarity.
Content Updates
• Over 180 HTML files have been updated.
• Rules have been revised, expanded and added to, making it easier to find relevant information and ensuring better clarity and compliance.
• All informational texts have been revised for clarity and readability.
• Design, colors, and HTML presentation have been refreshed for a cleaner and more modern appearance.
Design & Animation Enhancements
• Default iOS elements were replaced with custom-designed components.
• A custom segmented slider was introduced for key and central selections
• Preferences now use touchable feature boxes with round checkmarks instead of switches.
• A custom decision alert in the form of an info and selection box was added to provide clearer user prompts.
• Full table view reloads were replaced by intelligent partial reloads of only the changed sections to enable smoother animations.
New airport database
In-Flight Rest for Cockpit and Cabin Input Reworked
• Activating or deactivating rest now prompts for confirmation of the corresponding crew member (cockpit ↔ cabin).
• Safeguards were added to prevent unexpected behavior during user interactions with the table view (e.g., selecting or deselecting items multiple times).
• Custom animations provide smoother transitions during table view updates.
On-Block Time Input Reworked
• Code modernized for improved reliability and maintainability.
• Fixed an issue when selecting “Clear” (On-Block Time) without a previously set time caused errors.
Code Optimization
• Legacy iOS code and frameworks prior to iOS 15 were removed to unify the codebase.
• Special design layouts for smaller iPhone screens (4/4S/5/SE 1st gen) were removed.
• Removed the COVID-extended FDP rule for avoiding layovers on long-haul flights.
Error Handling and Fixes
Shared iCloud Sync (beta)
• Log files can now be copied to the clipboard.
• Added safeguards against unexpected characters in log files to prevent rare, non-reproducible crashes.
• Introduced queued writes for the same reason — to improve error handling and prevent write overload issues.
Used Airports List
• Added safeguards against unexpected characters to prevent one known non-reproducible crash.
General
• Additional safeguards were implemented throughout the app to help prevent similar edge cases.
