One sector at a time.
Save actual block events and crew duties locally, even without coverage.
Your roster
Tap a sector to open it in Flight Capture.
Recorded sectors
These records have not been synchronised to your verified master logbook.
Data & backup
Roster data and captured times stay in this browser on this device until you export them.
Import your planned roster
Choose your CSV and preview every change before saving. New flights can be added; identical rows are skipped; changes and potential duplicates require your approval. Captured times and manually entered crew remain protected.
Choose a CSV to preview. No changes are made until you approve them.
Export captured records
Use CSV to reconcile your captured blocks and PF/PM data against the iFlight report and your Google Sheet. Export JSON as a full restore-capable local backup.
Prepare for offline use · iPad
This app needs a downloaded offline shell before it can reopen without internet. Keep Wi-Fi connected during setup.
Checking offline readiness…
When ready, add Flight Capture to the iPad Home Screen in Safari. Test by turning on Airplane Mode and reopening from that icon. Flight records still stay on your device, not in Google Sheets.
App updates
App version 0.2.6 · civil twilight day/night suggestions and controls. When online, check for the latest app files without clearing saved flight data.
The app will reopen after checking online.
Google Sheets device sync · BETA
Optional Google-authorised synchronisation between iPad and laptop. Flight snapshots go into Device Sync; sectors with actual OFF and ON blocks are also staged automatically in Logbook Review Queue for pilot verification. Neither tab adds hours to Current LogBook. Stop and review conflicts before choosing which device to keep.
Not configured. No cloud flight records have been transferred.
Auto sync checks connectivity and credentials.
Automatic sync is ON by default: it uploads saved changes after a short delay and checks Google for new records roughly every 2 minutes while the app is open and authorised. Offline changes wait locally. After Google authorisation expires, tap Connect Google to resume. Conflicting edits are never silently overwritten. Manual Sync now remains available. Keep JSON backups.
Offline and synchronisation
Working now: browser-local records, UTC timestamp buttons, edit/undo, CSV and JSON export, and offline reopening after first successful installation via HTTPS.
Experimental: authenticated Device Sync journal; Google OAuth project setup and cross-device reconciliation are still required. Not connected: automatic approved-logbook import, native iFlight download, twilight classification. Continue independent JSON backups.
This is a personal record-keeping prototype, not an approved EFB or operational flight system. Never interact with it when doing so would interfere with aircraft duties. Device time can be incorrect: reconcile against operational records. Export backups regularly.
Privacy & device storage
No analytics or third-party tracking. Optional Google sync loads Google Identity Services and sends private flight snapshots only to the Google Sheets document you authorise. OAuth access tokens stay in memory, not in backups. Hosted app code may be publicly readable even though GitHub is private. Do not publish private CSV or JSON exports. Keep independent backups.