Logging Flight Time: What 14 CFR 61.51 Requires Pilots and Flight Schools to Record

A student arrives for the private pilot checkride, hands the examiner a logbook, and the practical test stops before it starts. One cross-country reads 49 nautical miles to the farthest point, not the 50 the rating requires. A night entry shows the flight but never tallied the landings. The pilot-in-command column does not add up to the aeronautical experience claimed on the application. None of these are flying problems. They are logging problems, and they are the kind a flight school can prevent long before checkride day.

The rules for what a pilot writes down live in 14 CFR 61.51. It is short, specific, and misunderstood often enough that examiners build extra time into every checkride to untangle a logbook. This article covers what the regulation actually requires, where pilots and schools get it wrong, and why the logbook is as much an operations artifact as a personal record.

What 61.51 Actually Requires

The regulation does not say a pilot must log every flight. It says a pilot must document the training and aeronautical experience used to meet the requirements for a certificate, rating, or flight review, and the recent flight experience used to satisfy currency under 61.57. Everything else is optional. In practice almost everyone logs everything, because the cost of a missing entry shows up years later when a job application or an insurance quote asks for totals that can no longer be proven.

When an entry is made, 61.51(b) sets the minimum content: the date, total flight time or lesson duration, the departure and arrival points or the route, the aircraft make, model, and identification, the type of experience or training, and the conditions of flight. A row that omits the night landings or the route is not a complete entry, and a checkride is exactly where that gap surfaces.

Flight Time Is Not Meter Time

The number that goes in the total-time column is flight time as defined in 14 CFR 1.1: from the moment the aircraft moves under its own power for the purpose of flight until it comes to rest after landing. That is block to block, and it does not match either meter on the panel exactly. It tracks closely with Hobbs and almost never with tach.

Schools that bill on one basis and log on another create a quiet trap for students who assume the invoice hours and the logbook hours should agree. They measure different things and rarely line up to the tenth. The cleaner a school is about which number means what, the fewer disputes land at the front desk. The full breakdown of why two meters exist is in our guide to Hobbs versus tach time; the short version is that the logbook follows flight time, billing follows the published basis, and maintenance follows time in service.

Who Logs PIC, and Why Two People Can at Once

The most common point of confusion in 61.51 is pilot-in-command time. Under 61.51(e), a pilot may log PIC for the time spent as the sole manipulator of the controls of an aircraft for which that pilot is rated. A student pilot flying a Cessna 172 they are rated to manipulate logs that time as PIC, even though the certificated flight instructor in the right seat is the legal pilot-in-command and is also logging PIC as the authorized instructor giving training.

Both entries are correct. Logging PIC and being the responsible pilot-in-command are two different ideas that happen to share a name. A renter who thinks the instructor cannot log PIC because the student is flying, or a student who refuses to log PIC because they are not yet certificated, has misread the rule. The sole-manipulator provision is what lets primary students build loggable PIC time from the first lesson.

Dual Received, Solo, and the Endorsements That Live in the Logbook

Training flights get logged twice. The student records dual received, and the instructor records flight training given, both with the instructor's signature or, in an electronic logbook, the instructor's certificate number and expiration. Solo time under 61.51(d) is logged when the student is the sole occupant, and it only counts as authorized solo when the matching solo endorsement is in the logbook.

This is where the logbook does double duty as a legal record. The endorsement for a flight review under 61.56, the solo endorsements, the 90-day solo renewals, and the authorizations for specific make and model all live as logbook entries. An examiner or an inspector reads the logbook to confirm not just hours but authority: that the flights the student flew were flights the student was signed off to fly.

Night and Instrument: The Columns That Trip People Up

Night and instrument conditions have their own logging rules because they feed downstream requirements. Night flight is logged during the period from the end of evening civil twilight to the beginning of morning civil twilight, and the night takeoffs and landings have to be counted separately to prove night recency later. Logging that a flight happened at night without recording the landings leaves the pilot unable to show currency when it matters.

Instrument time under 61.51(g) is logged as actual or simulated, with the location and type of each approach and the name of any safety pilot. A student building toward the instrument rating who logs approaches as a lump sum, without the individual location and type, has a record that satisfies nobody at the checkride. The aeronautical experience for each rating, spelled out in sections like 61.109 for the private certificate, is only as provable as the logbook columns behind it.

The Logbook Is an Operations Problem

Most logging failures are not knowledge failures. The pilot knows the rule; the entry just never got made cleanly while the details were fresh. A flight closes, the Hobbs reading and the route and the landings are all right there, and an hour later they are a guess. The school that captures flight time, conditions, landings, and the instructor sign-off at the moment the lesson ends has students whose logbooks survive a checkride without a scramble.

That is the same data discipline that keeps currency, billing, and maintenance honest across a busy fleet. Electronic logbooks are explicitly acceptable under 61.51, and a booking record that already knows the aircraft, the times, the route, and the instructor can populate most of an entry before the student touches it. HangarOS treats the flight-close step as the place that record gets made, so the logbook, the invoice, and the maintenance log all draw from the same flight instead of three transcriptions of it.

A logbook is the one document a pilot carries from the first lesson to an airline interview. Treat each entry as something a stranger will audit years from now, because eventually one will. The rule itself is short. Keeping the record clean across an active training fleet is a process the school owns, not a box the student checks alone.