Logging flights
This is the part of the app you’ll use every week. By the end of it you can enter a flight correctly the first time, put the times in so that the totals come out right, and know what happens to the aircraft and the people you typed that the logbook had never heard of.
Read C1 first. Everything else in this area is either a section of the same form or a shortcut into it.
| Guide | What it gets you | |
|---|---|---|
| C1 | Log a flight | One complete flight in the logbook, and every field on every section explained |
| C2 | Times, OOOI and time basis | Block times that produce the right Flight Time, including across timezones |
| C3 | Save as draft and finish later | A half-entered flight parked safely, and turned into a real one later |
| C4 | Aircraft, airports and crew that aren’t in your logbook yet | A flight logged in an aircraft, or with a person, the app has never seen |
| C5 | Takeoffs, landings and approaches | The counts currency reads, and instrument approaches on the record |
| C6 | Add photos to a flight | Photos onto a flight, and back off it |
| C7 | Capture times from the FMC | The four block times read off a photograph of the FMC page |
| C8 | Edit several flights at once | One value set across many flights in a single pass |
Three things worth knowing first
The entry form is one form with one Save. There’s no Next, no Back, and nothing is checked section by section. On a phone it’s one scrolling page of cards you open and close; on a desktop it’s a dialog with a list of sections down the left. Either way, move around it in whatever order you like, and a single Save checks everything at once.
Which sections you see is a setting. Every section except Times can be hidden, along with a number of individual fields, from Profile Settings → Entry Form — Show or hide sections and fields when logging a flight. So if a guide here names a section that isn’t on your form, that’s where you turn it back on. Hiding a section hides the place to type; it doesn’t clear what a flight already holds.
There are three ways in. The Add Flight button at the bottom of the logbook, the Log Flight quick action on the dashboard, or tapping a flight card and then Edit. The first two create a new flight, so the free tier’s 100-hour limit applies to them (→ K2). Editing a flight you already have is never limited.
Words this area introduces
Block time — the time from Out (Blocks Off) to In (Blocks On): chocks to chocks, not wheels to wheels. This is the number the app calls Flight Time, and it’s what every total in the app is built from.
Air time — Off (Takeoff) to On (Landing): wheels up to wheels down. It’s a separate field, and never the number the totals use.
OOOI — the four block times together: Out, Off, On, In. The app uses those four letters as field labels and heads the group Block Times.
Time basis — a per-flight declaration of which clock the four OOOI times were written in: UTC / Zulu, or Airport local. It changes how Flight Time is worked out, not how the times are saved.
Tach — the airframe’s tachometer reading, entered as a start and an end number. The difference between them is a fallback source for Flight Time.
Draft — an entry saved before it was complete. It sits in the logbook list as an amber DRAFT card and counts toward nothing until it’s finished and saved again.
Bulk edit — setting the same value on several flights at once, using the same entry form.
Memories — photos attached to a flight. They’re not part of the regulatory record, and they live on the flight’s detail view rather than in the entry form.
FMC capture — photographing the aircraft’s FMC, MCDU or FMS page and letting the app read the block times off it.