Keep your §61.51 logbook

Your logbook is a portable §61.51 record — it belongs to you, not any one operator, and follows you between them. It's available both on the crew web portal and in the mobile app; this page covers both.

Reading your logbook

1. Open Logbook (web: /crew/logbook; mobile: the Logbook tab). You get your all-time totals — total block hours, PIC hours, night hours — and a list of recent flights.
2. Tell synced entries from manual ones. Every entry carries a source: entries derived automatically from a closed leg you flew on-platform are synced/platform entries; entries you typed yourself are labeled manual/crew-entered. A manual entry is your own record of an off-platform flight — it is never shown as verified or operator-confirmed.
3. Check your §61.57(a) recency, on mobile. The mobile logbook screen also computes a 90-day takeoff/landing recency self-check (3 takeoffs/landings carrying passengers in the preceding 90 days) from your synced entries. It's explicitly a self-check, not an operator-verified currency claim — a window with no qualifying data reads PENDING, never a fabricated "current." (The web currency view covers the broader qualifications picture and is documented separately.)
4. Filter and inspect, on mobile. Role and date-range chips filter the list and recompute subtotals over what's visible — the all-time summary stays the authoritative figure; a filtered subtotal is labeled accordingly. Tapping a row opens the night/IMC/approaches/landings breakdown the list view doesn't show inline.
5. Export. Both surfaces offer a CSV export; the web portal also offers a PDF download.

Adding a manual entry

1. Tap/click Add entry.
2. Fill in the flight date, your role (PIC/SIC/FA), route, tail, block time, night/IMC time, approaches, and day/night landings.
3. Save. On mobile, the entry is queued to your local write-queue first (so it survives no signal) and synced when you have a connection, using the same offline pattern as everything else in the app — never lost, just queued until it can send.

Honest state of the route/tail fields

The web logbook's From and To fields resolve through the shared airport picker, so a route can't be mistyped. Tail and Type remain free text on the web form by design — this form also has to log flights an operator's fleet list can't represent (another operator, recurrent training, personal flying), so constraining tail to your current tenant's fleet would wrongly narrow what you can record.

The mobile entry form is not yet on the picker — From, To, and Tail are all free text there today, guarded only by uppercase auto-capitalization. If you jump into the form via Log this leg from a completed leg, those fields arrive pre-filled from the leg itself, so you're typing less in practice even without a picker.