CrewCaddy is the logbook app for airline crews: your roster arrives on its own, flight time limitations are checked against the actual EASA tables — and where a rule isn't modelled yet, the app says so instead of guessing. Your logbook stays on your device.
For iOS (TestFlight) — free to use, and export stays free for good.
Everything a crew logbook has to do — and honest about what it doesn't do yet.
Connect your crew portal once (Wizz Air eCrew today) and duties, flights and crew names come in automatically — with a change journal instead of silent overwrites. Roster PDF and calendar import work for everyone else.
FDP, cumulative limits and rest per EASA ORO.FTL — every value carries its regulation reference, home-base history included. Where a rule isn't modelled, CrewCaddy says “not assessable” instead of inventing a number.
Flights, duties and signatures live in a local database — fast with 5,000+ flights, usable offline. Only what you explicitly connect ever talks to a server.
Take over your logbook from LogTen or Safelog. Flights that exist in both are matched by date, registration and route — reading a file twice never creates duplicates.
Encrypted archives with a recovery code only you hold. Every backup is re-opened and counted right after writing — an unreadable backup is worse than none. A restore test is built in.
CSV export profiles and the EASA FCL.050 PDF printout work without a subscription — and keep working after one ends. Your data is never held hostage.
Set up once. After that, flying is the only input CrewCaddy needs.
Import your existing logbook from LogTen or Safelog and set your home base — including former bases, because old duties are judged by the base you had back then.
Sign in with your crew portal credentials. They're checked live, transmitted once, and never stored readable on the server. No airline in the list? PDF and calendar import work just as well.
The roster arrives, flights land in the logbook, FTL and currency update themselves. Anything you've signed and locked is never touched by an import.
CrewCaddy is built by a line pilot who reads his own privacy policy.
The logbook is a local database. No account is required for logging, FTL, import, export or backups — the account exists only to fetch your roster.
Roster sync runs against our own server in the EU — no third-party cloud, no analytics, no trackers, no ads. Your portal password is encrypted with a public key the API cannot even decrypt.
Free export in open formats, encrypted backups you hold the key to, and an unlink button that deletes your credentials from the server. Leaving CrewCaddy is a feature, not a support ticket.
The beta is free. Pricing for the finished app isn't final yet — but one thing is decided: export and your data stay free forever, with or without a subscription.
Wizz Air (eCrew/AIMS) today. Others follow as soon as their fetch runs reliably — a list full of names that don't actually work would be a promise the app can't keep. Roster PDF and calendar (ICS) import work for any airline.
No. It follows EASA ORO.FTL with source references on every value, and clearly marks what is provisional or not modelled (e.g. reduced rest). It supports your judgement; it doesn't replace your operator's system or your responsibility.
iPhone with iOS 17 or newer, in English, German, Romanian, Spanish, French, Italian and Russian. There is no Android version yet — we'd rather say that here than in an app store review.
It's transmitted once to verify, encrypted with a public key whose private half never touches the API server, and used only to fetch your roster. Optionally it's stored in your device's keychain — never in a backup, never on our database in readable form.
Send a short note with your airline and fleet — you'll get a TestFlight invite shortly after.