What should an airline pilot record in a logbook?

Updated September 2026 · 5 min read

What you must record depends on your authority and your operation. Most professional logbooks come down to the same building blocks.

The flight itself

The date, the aircraft type and registration, where you departed and arrived, and the out and in times, usually in UTC.

Flight time and your role

The total flight time, and how it counts for you: as pilot in command, as second in command or co-pilot, as multi-pilot time, or under supervision, using your authority's definitions.

Conditions

Night time, instrument time (actual and simulated) and cross-country time, each as your authority defines it. Definitions differ, so use the one that applies to your licence.

Takeoffs and landings

Day and night takeoffs and landings, which is how recency is usually shown.

Simulator, training and remarks

Simulator sessions, training given or received, checks, and remarks or endorsements. Some logbooks also ask for the name of the pilot in command.

Totals and certification

Page totals, the amounts brought forward and the totals to date, and your signature certifying the entries.

Planned times versus actual times

If your entries start from a roster, check them against what actually happened. Relief time on augmented crews and changes on the day are the usual places where the plan and the record differ.

How G Force Logbook and Scheduling helps Each flight is logged with its out and in times, route, aircraft and crew, with night time, takeoffs and landings worked out by your rules, and prints in the FAA, Transport Canada or EASA columns with totals and your signature on every page.

General guidance for crews, not legal advice. Rules differ between authorities and operators: check the ones that apply to you.