What data syncs across devices?

Pilot Kit currently syncs flight logs, aircraft profiles, checklists, and GPS track logs. Those are the entity types wired into the current sync service.

Does Pilot Kit still work offline?

Yes. The app is offline first. You can keep editing locally, and pending changes are uploaded when the device reconnects.

Which plans include cloud sync?

Cloud sync is available on Pro and Operator. Plus remains the local-backup tier, while cloud sync is part of the higher multi-device workflow.

Can I manage connected devices?

Yes. Dashboard includes a device management view where you can inspect connected devices, see last sync time, reset a device sync state, or remove a device from the account.

What happens if there is a sync conflict?

Pilot Kit marks the conflict, surfaces it to the user, and supports resolution paths that prefer local data or remote data depending on the recovery decision.

Is cloud sync the same thing as local backup?

No. Local backup is a single-device safety copy. Cloud sync is the multi-device workflow that keeps operational records aligned across signed-in devices.

Cloud sync for pilots

Keep flight logs, aircraft, checklists, and track logs in sync across your devices

Pilot Kit cloud sync is built for real pilot data: flight logs, aircraft profiles, checklists, and GPS track logs. Pro and Operator subscribers can enable sync, keep working offline, and let the app reconcile changes when they are back online.

Download the App See Pricing

Cloud sync control center

See queued changes, recent sync activity, and device health before the next flight.

Cloud sync for pilots

Last sync

2 minutes ago

Queued changes

3 waiting

Connected devices

4 total

Entity sync status

Offline queue and recovery

Flight logs Synced

Aircraft Pending

Checklists Syncing

Track logs Conflict review

Connected surfaces

iPhone

iPad

Android tablet

Dashboard

Offline queue and recovery

Changes queue locally, then upload and reconcile when connectivity returns.

dashboard

Open Dashboard

Dashboard shows connected devices, last sync time, and reset actions for drifted clients.

Connected devices

4 total

Last sync

2 minutes ago

Reset a device sync state

If one client drifts, reset its sync state so it re-downloads all data on the next clean sync.

Open Dashboard

What syncs

The records pilots actually need on every screen

The sync layer is not generic file storage. It is wired into the records pilots edit during real flying, training, and fleet operations.

Flight logs

Keep logbook entries aligned across your phone, tablet, and other signed-in devices.

Aircraft profiles

Sync aircraft details so performance planning and records stay consistent everywhere.

Checklists

Carry checklist libraries and completed execution data across devices without re-entering them.

GPS track logs

Upload recorded track data and pull it back to another device when you need to review or export it.

How it works

Offline first, then reconcile when you are back online

Cloud sync is opt-in. Once enabled, Pilot Kit keeps a local queue, pushes local changes, and pulls newer server data with incremental sync and full sync tools when needed.

Enable sync after sign-in

Cloud sync stays off until the user explicitly turns it on, which keeps control with the pilot and the account owner.

Keep working without signal

Edits can stay local first. The app records pending changes and waits until the device is back online.

Upload, pull, and reconcile

The sync engine pushes local changes, downloads newer server data, and refreshes the last sync state.

Run manual or full sync when needed

Pilots can trigger a normal sync, a full sync, or a device reset path when data needs a clean re-download.

Enable sync after sign-in

Cloud sync stays off until the user explicitly turns it on, which keeps control with the pilot and the account owner.

Keep working without signal

Edits can stay local first. The app records pending changes and waits until the device is back online.

Upload, pull, and reconcile

The sync engine pushes local changes, downloads newer server data, and refreshes the last sync state.

Run manual or full sync when needed

Pilots can trigger a normal sync, a full sync, or a device reset path when data needs a clean re-download.

Control and recovery

See devices, resolve drift, and recover safely

The new sync stack exposes state instead of hiding it. Pilots can see what happened, which device is involved, and what to do next.

Connected device management

Dashboard lists connected devices, their platform, app version, online or offline state, and last sync time.

Reset a device sync state

If one client drifts, reset its sync state so it re-downloads all data on the next clean sync.

Conflict handling

Pilot Kit detects conflicts, surfaces them, and supports local-first or remote-first resolution paths.

Cloud-backed continuity

The sync layer is paired with cloud-backed storage and safety checks so pilots are not depending on one device alone.

Status visibility

Sync state is visible, not hidden

The app surfaces the states pilots and ops teams actually care about while editing live records.

Synced

Local and cloud data match.

Pending

Local edits are waiting to upload.

Syncing

A sync cycle is running now.

Conflict

Local and cloud changes need review.

Error

A sync action failed and needs attention.

Upgrade required

Cloud sync is gated by plan access.

Cloud sync FAQ

Cloud sync for pilots

Start with one device, keep going everywhere

Use Pilot Kit on the device you fly with today, then turn on cloud sync when you need your operational records to follow you across screens.

Download Pilot Kit Compare Plans Open Dashboard