Watch your duty and rest

The Duty tab is your at-a-glance duty legality view, computed by the FTL engine from your recorded duty facts. It is currently mobile-only — there is no separate duty/FTL view in the crew web portal.

Steps

1. Open the Duty tab. It fetches your duty-status snapshot and also keeps the last one cached on your device, so it still renders offline — with an "as of" timestamp so you know how current it is.
2. Check in and out of duty. The Check in / Check out buttons record the start and end of a duty period. Like every write in this app, a tap is queued locally first and synced when you have a connection. The legal transition — you can't check in twice without checking out, or check out with nothing open — is enforced by the server; the app surfaces that as a conflict message rather than pretending the tap worked.
3. Read the top banner. It reads FTL compliant or FTL blocking based on all_crew_compliant from the synced snapshot — never from your local check-in/out taps alone. If the snapshot on screen is stale (cached past a staleness threshold) and it was compliant, the banner degrades to PENDING_VERIFICATION rather than keep showing a green that might no longer be true; a stale blocking result is always kept, never hidden.
4. Read the FDP timeline and countdown. The bar shows flight-duty-period hours used against your limit, live-extended by the wall clock since the engine last computed it (an open duty period keeps burning FDP). A Time to FDP limit countdown ticks down the same way. When the engine could not establish a limit for you, both read PENDING_VERIFICATION instead of drawing a fabricated bar or clock.
5. Read your rest accrual. A running tracker shows rest accrued since your last duty period ended, live-extended the same way. The exact wall-clock time you're next legal to fly lives behind an operator-side endpoint this screen does not call, so Legal to fly again at always reads PENDING_VERIFICATION here — the app shows what it actually knows (rest accrued) and does not compute a precise legal time it can't back up.
6. Review recent flight-time windows. Below that, a history section lists your rolling flight-time accumulation — last 24 hours, calendar quarter, two consecutive quarters, calendar year — each against its limit where the engine has one. This is real engine output, not a fabricated log of past duty periods.
7. Check blocking violations and citations. If the engine found any blocking violations, they're listed with their regulatory citation.