Guides · 15 November 2026
Can AI read a handwritten pilot logbook? What we measured
"AI logbook" can mean anything from a chatbot bolted onto a flight list to a system that reads your paper logbook. This article is about the second: photographing a handwritten page and getting structured flights back. We build one, so we measured it, and here is what we found — including the parts that still need a pilot.
How it works
- You photograph a page. Flat, in even light, all four corners in view. A phone camera is plenty.
- The page is read row by row into the columns of the logbook: date, type, registration, crew, every time column, take-offs and landings, approaches, route and remarks.
- Every field gets a confidence score. Not the row, each field, because a row can have a perfect date and a doubtful registration.
- The reading is checked against itself. The page's own "Page Totals" line is read too, and the columns are added up and compared. An hour misread anywhere on the page shows up as a column that doesn't match.
- Registrations are checked against the aircraft registers, using the aircraft type: a misread tail on a Cessna 152 usually has exactly one registered 152 one letter away.
- You review. Doubtful fields are shown in orange. Nothing goes into the logbook until you confirm it.
How accurate is it?
We test against hand-verified pages of real, handwritten logbooks. On the version deployed on 12 November 2026:
- 99.5% of flights found.
- 99.2% of hours exact to the tenth.
- 100% of take-off and landing counts written on the page read correctly.
- 97.4% of identity fields correct before the pilot touched anything — date, type, registration, names, route.
- 99.98% agreement on the grand total between the hours Hobbs adds up and the totals printed on the pages.
- About 28 seconds a page.
The full method is on our accuracy page.
What it still gets wrong
- Registrations. About one in ten is misread first time, mostly look-alike letters (Q/O, U/V, H/M) in a hurried hand. This is why registrations are checked against the registers and, when still in doubt, against the flights that aircraft actually flew that day.
- Names. Instructors' and students' names in cursive are the hardest text on a page.
- Things that aren't on the paper. No reader can recover a landing that was never written down. A good one points out the gap (hours logged but no landings) rather than inventing a number.
What makes it safe to trust
A reader that is 99% right and gives no sign of the other 1% is dangerous in a legal record. The safeguards matter more than the headline number:
- per-field confidence, so you know where to look;
- the page-totals check, so a wrong hour can't hide;
- nothing saved without review;
- an audit trail of every change you make afterwards.
It gets better as you use it
When you correct the same misreading twice, later pages are corrected for you and marked "Learned" with an Undo. It learns identity text — registrations, types, names, airports — and never your hours. An unusual flight time is flagged as a question, never "fixed".
What it costs
In Hobbs, scanning is counted in flights, about ten to a page, and only flights you import are charged. A page that fails to read, a scan you cancel or a half-full page never costs more than the flights actually added. Every account gets 20 scanned flights free, and the logbook itself is free.
Try it on two pages of your own logbook — your handwriting is the only test that matters.