Separate local access from cloud confirmation
Army Flight Logbook’s website describes local device storage and syncing after connectivity returns. That creates two moments worth checking: whether a record is available on the device, and whether its latest changes have reached the account’s online data.
Prepare before losing connectivity
While online, sign into the correct account and confirm that the records you need are visible. Review the current app’s offline instructions before relying on a feature away from connectivity. Do not assume every platform, account action, or report works identically offline.
For a first test, use a safe, non-operational setting. Learn how your app communicates connection and sync status while you can still reach support. Do not make an unfamiliar workflow part of a time-critical task.
Verify after reconnecting
Once connected, follow the app’s sync process and inspect a record you changed offline. If you use another device, confirm the expected change there after synchronization completes. Avoid editing the same record in several places while investigating a mismatch.
If the change is missing, write down which device contained it and when you last confirmed it. Do not uninstall the app or clear its storage as an initial troubleshooting step when unsynced records may remain locally.
Report the state precisely
A useful sync support request identifies the app version, device, connection state, and whether the record is present locally or on another device. Share only information permitted by your organization. The aim is to describe the sequence clearly without exposing unnecessary record details.
Your records. A clearer next step.
Explore Army Flight Logbook · Get product support · Browse the guide collection
These are product and personal record-organization guides, not official Army instructions or flight authorization. Follow applicable unit guidance and information-handling requirements. Feature availability and screen details can vary by version and account.