A pilot in the r/flying community has raised a pair of technical support questions regarding LogTen Pro, the widely used electronic logbook application for professional and general aviation pilots. The first issue involves simulator time being erroneously categorized as SIC (Second-in-Command) time within the app's Pilot Credentials Report, despite the user having reviewed and reconstructed their smart group logic in an attempt to isolate the cause. Notably, only a subset of the logged simulator sessions are affected, suggesting a possible inconsistency in how individual log entries are tagged, how smart group filters are being applied, or how the app's underlying data model differentiates simulator time from actual flight time when categorizing crew position. The second issue is a discrepancy in the Resume Report, where total logged hours appear roughly 150 hours short when compared against the sum of PIC, SIC, and dual received time recorded elsewhere in the logbook—pointing to a possible bug in how the report aggregates time categories or excludes certain flight types from its summary calculation.
For working pilots, especially those pursuing airline, corporate, or Part 135 careers, logbook accuracy is not a trivial administrative matter—it is foundational to regulatory compliance, career progression, and insurability. Electronic logbooks like LogTen Pro are widely trusted to generate the official records used for FAA certificate applications, ATP minimums verification, airline and fractional operator hiring packages, and insurance underwriting. A pilot presenting a resume or logbook summary with unexplained hour discrepancies—particularly one that misrepresents SIC time earned in a simulator versus SIC time earned in an actual aircraft—risks credibility problems during interviews, checkride eligibility reviews, or FAA audits. Simulator time, in particular, is subject to strict regulatory distinctions (e.g., 14 CFR 61.51 logging requirements and differences between FTD/FFS credit and actual flight time), and any software-level miscategorization could inadvertently overstate or misstate a pilot's actual flight experience if not caught and corrected before submission to an employer or the FAA.
This scenario also reflects a broader and increasingly consequential trend across aviation: the industry's near-total reliance on digital logbook platforms—LogTen Pro, ForeFlight Logbook, MyFlightbook, and others—as the system of record for pilot experience, often with minimal independent verification against paper backups. As airlines, fractional operators, and flight departments increasingly request digital exports or app-generated summary reports directly during the hiring and records-verification process, software bugs or user-configuration errors carry higher stakes than in the paper-logbook era. Smart groups, custom categories, and automated report templates—while powerful for efficiency—introduce complexity that can obscure errors, particularly for pilots with mixed flying backgrounds (e.g., transitioning between military, flight instruction, corporate, and airline SIC time) where crew position and aircraft category logging conventions vary.
Threads like this one on r/flying also illustrate the aviation community's reliance on peer crowdsourcing to troubleshoot software issues that formal vendor support may be slow to resolve. Pilots evaluating or currently using LogTen Pro should treat this as a reminder to periodically audit smart group definitions, cross-check automated reports (Pilot Credentials, Resume, Currency) against raw logbook totals, and maintain redundant backups or exports before relying on any single digital report for a job application, checkride, or insurance submission. As logbook software continues to evolve with cloud syncing, multi-device entry, and increasingly automated categorization, the burden remains on the individual pilot—not the software—to verify that reported totals accurately reflect actual, regulation-compliant flight and simulator experience.