FLIGHTLEDGER / PRACTICAL GUIDE
Logbook totals reconciliation: decimal hours, H:MM and overlapping time
Many apparent total mismatches come from overlapping columns, missing values or different rounding methods. Compare like with like.
By Zijian Xiao · Updated November 7, 2026
Convert the unit before comparing
Decimal 1.50 hours is 90 minutes, shown as 1:30. A value written 1.30 is 78 minutes in decimal-hour mode, but 90 minutes in H.MM mode. Select the source convention explicitly. Colon values such as 1:30 are always hours and minutes. FlightLedger rounds each entry to the nearest minute before summing and exports decimal hours to two places.
Do not sum overlapping columns
For a 1.5-hour flight, 1.5 PIC, 0.5 night and 1.0 cross-country can all be true. Their sum is not supposed to equal 1.5. The report checks each component against total time with a one-minute rounding tolerance. PIC plus SIC exceeding total is a warning to inspect roles, not an automatic legal conclusion.
Compare coverage as well as totals
If only 10 of 100 rows contain instrument time, the instrument sum is a known subtotal, not a verified career total. Our summary lists rows with a value alongside total flight rows. An empty cell stays blank in exports. A typed zero is a known zero. No missing time is inferred from other columns.
Check landings and duplicates separately
Day and night full-stop landing fields may not include touch-and-go landings. A difference from total landings requires checking the source definitions. Exact duplicate records stay included in totals until you remove them in the original and upload a corrected file. Dates with multiple flights are not automatically errors. Gaps between flight dates are normal and are not treated as missing flights.
Start with your own file.
See the full automated report and 20 converted rows before paying. A complete export starts at $19. Files expire after 24 hours.
Review my logbook free