MODULE 02
Logbook import
Three hundred jumps in a paper logbook mean an evening of retyping, which is why most of them never get moved at all. A photo of the page goes to the server and comes back as a table of rows: the app fixes the obvious itself, flags the doubtful with a reason, and you check it and add the whole page in one tap.
How it works
01The photo
Camera, or a file you already have. Before the first shot — a short hint: the whole page in frame, even light, no shadow across it.
02Recognition
The page goes to the server and comes back as jump rows in about half a minute. Columns are read from the header: both Russian logbook formats and foreign ones.
03Checking
The table is shown in full — no row is hidden or collapsed. Suspicious cells are highlighted with a reason; you edit a single cell or a whole block.
04Adding
“Add N jumps” and the page lands in your logbook as one batch. While the result screen is open, the import undoes in one action.
What the app checks on its own
Unreadable number
“2S4” between 293 and 295 is restored by arithmetic — and the cell says so honestly: derived, not read.
Gap in numbering
232, 234 — a gap is never closed silently. Gaps are often real, so the row becomes a question for you.
Date from above
An empty date cell means “same day”, exactly as in the paper book: the date carries down. An empty date in the first row is a genuine blank.
Dates don't run backwards
A date that moves back while the number grows gets flagged — which also catches an instructor's slip: 06.05 between 31.05 and 18.07.
Date order
A page that reads both as DD.MM and MM.DD is run through both readings; the one that keeps the order survives. If both do, you decide.
Odd one out
A Safire 119 among twelve Safire 149s gets flagged: in a run of identical values, the outlier is almost always a misread rather than a fact.
Catalogs
Canopies, aircraft and dropzones are matched against the app's catalogs. What doesn't match stays as raw text with a note instead of being swapped for something similar.
The club stamp
A name and city read from the stamp are offered as a hint for a block of rows — never filled in silently.
Checking you can trust
Everything visible
The page is shown whole: highlighting helps you look, it doesn't decide for you which rows deserve attention.
Edit by block
“All fifteen of these are a Safire 149” — one action changes the block. Cell-by-cell editing stays available.
Where a value came from
Every value shows its origin: read, inherited, derived, normalized or edited by you. Nothing is corrected silently.
Deliberate blanks
Before adding, a plain question: “5 of 15 jumps have no dropzone — leave them, or go back and fill them in?”
What lands in the logbook
The whole page
Rows are written as a single batch: there is no such thing as half an imported page.
Duplicates skipped
A jump whose number is already in the logbook is not overwritten — what you entered by hand wins. The report says: “13 added, 2 skipped”.
Your total stays put
The offset for jumps made before the app is left alone: moving the paper book doesn't double your count.
Undo
Changed your mind — “Undo import” removes exactly the jumps this page created.
Limits and privacy
50 pages free
What's left is on the capture screen before the shutter, not after the work is done. The limit is counted in pages — never in jumps.
Manual entry is unlimited
Adding jumps by hand is unlimited and always free. Only automatic recognition is capped: every page costs real money on our side.
The photo isn't kept
The picture of the page is stored neither on the server nor in the cloud. The recognized table lives for a limited time — so you can come back to the page without spending another one.
Nothing gets lost
The draft survives backgrounding and restarts. No network, or no pages left — you're told before processing, and the page isn't spent.
Move your paper book
Fifty pages of recognition are free — more than enough for most logbooks, and the rest can always go in by hand. All that's left is to get the app.