A junior flight instructor's logbook error, surfaced on r/flying, illustrates a persistent and often underappreciated compliance pitfall in flight training: the distinction between landings flown as sole manipulator of the controls versus landings occurring during a lesson in which the instructor was PIC but not physically flying the airplane. The CFI in question logged every landing completed during roughly 400 hours of dual given as though each was personally flown, when in fact many were performed by students under instruction. Over seven months this inflated the instructor's personal landing count by several hundred, creating a logbook that overstates currency-qualifying and experience-qualifying landings. Because the entries were made in ink in a paper logbook, the error cannot simply be erased, forcing the instructor to consider a corrective methodology — likely a dated "logbook audit correction" line item — before migrating to an electronic logbook.
This scenario matters because landing totals are one of the few objectively verifiable, frequently scrutinized data points in a pilot's logbook, and they carry both regulatory and career weight. FAR 61.57 currency requirements (three takeoffs and landings within 90 days, with additional stipulations for night and tailwheel operations) depend entirely on landings the pilot personally executed as sole manipulator; landings flown by a student, even under an instructor's supervision and even when the instructor is legally acting as PIC, do not count toward the instructor's own currency. Regional airlines, fractional and charter operators, and insurance underwriters for business aviation also weigh total landing counts alongside flight hours when evaluating experience, particularly for pilots transitioning into multi-crew or high-performance aircraft. An instructor who cannot substantiate an accurate landing count risks not only a currency violation — a legal issue if discovered during an FAA ramp check, checkride, or accident investigation — but also credibility damage if a hiring board or check airman later questions logbook accuracy during background verification.
The instructor's proposed fix — reconstructing a conservative, defensible minimum landing count sufficient to demonstrate continuous 61.57 compliance, rather than attempting to reverse-engineer an exact historical total — reflects sound risk management. Auditors and hiring departments generally care less about a precise landing tally than about internal consistency, honesty of correction, and absence of currency lapses. A documented, dated correction entry explaining the methodology (e.g., "landings restated to reflect sole-manipulator flights only; prior entries overstated") creates a defensible paper trail that shows good faith rectification rather than concealment, which is the posture the FAA and prospective employers care about far more than the absolute number.
This case also reinforces a broader trend across flight training and early-career aviation: the rise of electronic logbook platforms (ForeFlight, LogTen, Garmin Pilot) that enforce clearer field separation between PIC time, dual given, landings as sole manipulator, and instructional landings, reducing the ambiguity that produces errors like this one. As flight schools scale up to meet airline pipeline demand and CFIs accumulate hours rapidly to reach ATP minimums, logging discipline early in a career has outsized downstream consequences — errors compound across hundreds of lessons before they're caught, as this instructor discovered. The episode is a useful reminder for CFIs, DPEs, and chief instructors alike to periodically audit logging conventions with new instructors, and for any pilot transitioning logbook systems to reconcile category definitions rather than assume continuity between paper conventions and digital templates.