How to scan a paper logbook page with DaPilot

Most pilots inherit a stack of paper logbook pages. Sometimes hundreds. Typing those rows into a digital logbook is the second-worst part of switching apps (the worst is finding out the new app drops some of your fields). DaPilot's OCR scanning reads any standard paper logbook page and writes the rows for you. You review and save. A typical page takes about thirty seconds end-to-end.

This guide covers how to take a good photo, what DaPilot reads, what it does not, and the things that trip up the model.

Why this matters

The longer you put off digitizing your old paper logbook, the more brittle it gets. Coffee stains. Lost pages. The page you flew through Vegas in 2019 that you cannot find. OCR scanning lets you do this opportunistically: one page tonight, two pages tomorrow, all of it digitized over a couple of weeks instead of a brutal Saturday.

What you need

DaPilot Pro, or the one free OCR scan still available on the free tier.
The paper page in front of you.
Decent light. Direct overhead sunlight or a desk lamp positioned to remove shadow.
Reception (the model runs server-side).

How to take a good photo

The model reads almost any standard paper logbook page (ASA, Jeppesen, Cirrus, airline-issued formats). The hard part is the photo, not the OCR.

1Flatten the page

If your logbook is bound, press the page flat against the desk. The crease near the spine compresses rows and the model misreads them. If you have to hold the page open with one hand, hold near the corner so your hand is not in the photo.

2Frame the whole page

Get the entire page in frame, including the column headers at the top and any totals row at the bottom. The model uses headers to map columns. If you crop the headers off, accuracy drops fast.

3Light it evenly

Direct sunlight from above is best. Indoor lighting is fine if you avoid shadow lines across the page. Avoid the iPhone flash; it tends to glare on glossy paper.

4Hold the iPhone parallel

Tilt the camera until the page edges are roughly parallel to the photo edges. Slight perspective distortion is fine. Severe perspective (camera way off-axis) is not.

5Take the photo

Tap the plus button on the dashboard, pick Scan paper logbook, and either capture a new photo or pick one from your photo library. The image goes to the OCR endpoint. You'll see a "Reading the page" screen for about ten seconds while the model works.

What DaPilot reads

The model is trained on real paper logbook pages and handles a long list of edge cases. Things it gets right:

Column auto-mapping. The model reads the column headers (Date, Aircraft Type, Aircraft Identification, Total Time, PIC, SIC, etc.) and figures out which column is which. You can have columns in any order; the model maps them.
Ditto marks. A dash, double-quote, or // in a column means "same as the row above." The model copies the value forward.
Crossed-out corrections. If a number is struck through and a corrected number written next to it, the model takes the correction and flags the field with an uncertainFields entry.
Touch-and-go vs full-stop. Most paper logbooks abbreviate as T/G, TGL, FS, or just two columns. The model maps them correctly.
Decimal vs colon time formats. 1.5, 1:30, and 1+30 (Garmin format) all read as 1.5 hours. Ambiguous values like 1.30 get flagged for review.
Date format detection. M/D/Y vs D/M/Y is auto-detected from European cues. If you flew in a country that uses 24-hour times and D/M/Y dates, the model picks that up.
Skipping totals rows and endorsement blocks. Total rows at the bottom of the page do not become flights. Endorsement signature blocks do not become flights.

What DaPilot does not read

Handwriting that is genuinely illegible. If you cannot read your own writing, the model probably cannot either. The cell gets flagged.
Watermarks or background noise. Heavy security backgrounds on some airline-issued logbooks confuse the model. You may need to retake the photo on a contrasting surface.
Pre-printed signature lines as flights. The model is good at this but very occasionally drops a signed checkride row. Review the page.

6Review every row

The review screen shows each parsed flight as an editable row. Anything flagged uncertain has an amber pill. The order on screen matches the order on the page, top to bottom.

For each row, check:

Date matches the row on the page.
Aircraft tail and type match.
Total time matches.
PIC, SIC, dual, etc. match. Per-row sanity check: no individual time field exceeds total time. If the model produced one that does, the row is flagged.
Approaches and landings match.

Edit anything wrong. The form is the same one you'd use for manual entry.

7Save the page

Tap Save all. Every row lands on the dashboard with the correct date order. Currency and totals refresh. If you scanned a page from 2019, those flights show up dated 2019 and roll into your historical totals, but they do not affect your 90-day currency window.

Free trial limits

The free tier ships with one OCR scan. The counter does not reset; once you've used it, OCR is paywalled until you start Pro. Pro is unlimited.

Backlog strategies

If you have a stack of paper logbooks, scan the most recent year first. Currency math runs on the last 90 days, so a recent page closes the gap fastest. Older pages do not unlock new currency events but they do contribute to your career totals (turbine PIC, total time, etc.) which matter for hiring.

Most pilots get through about ten pages an hour at a steady pace. A 100-page paper logbook is one weekend.

Common pitfalls

Photographing a curved page (book bound on a deep spine). The crease distorts the rows nearest it. Press the page flat or photograph each side separately.
Cropping off the column headers. Without headers, the model has to guess which column is which and accuracy drops sharply.
Trying to scan a multi-page spread in one photo. Photograph one page at a time. The model is tuned for single-page layouts.
Using the iPhone flash on glossy paper. The glare obscures rows. Use ambient light.
Skipping the review step because the page looks fine. Open at least three rows to spot-check; the model is right almost always but the cost of a wrong row is high.
Re-scanning a page you already scanned. Duplicates are detected by date plus route plus tail, but if a row's data was edited between scans, the dedupe might miss it. Scan each page once.

Tips from pilots who already migrated

Scan the page in chunks of five rows if the page is dense (some airline logbooks pack 25 rows per side). Take two photos of the page, top half and bottom half, with overlap. The model is more accurate per-row when the input image has fewer rows.

If you have a logbook in a binder, take it out of the binder before scanning. The binder rings throw shadows that confuse the column detection.

After the first few pages, you'll get a feel for which of your old pages have ambiguous handwriting. For those, photograph a second time with stronger light or accept that two or three rows will need editing.

Last updated April 27, 2026 · 9 min read