Log a flight

What this does

Puts one complete flight into your logbook, and shows you what every field on every section of the entry form is for.

Before you start

• A profile is open (→ A3).
• Five things are required, and the app lists them in its own checklist: Flight Date, Aircraft, Departure Airport, Arrival Airport, and Total Time (Times or Manual). Everything else is optional. If you don’t have all five yet, you can save the flight as a draft — an entry that sits in your logbook and counts toward nothing until you complete it (→ C3).
• On the free tier, you can’t add a new flight once your logbook passes 100 hours (→ K2). Editing a flight you already have is never limited.

Steps

1. Tap Add Flight at the bottom right of the logbook, or Log Flight on the dashboard. The form opens, titled New Flight.

   Expand

   On a phone, it’s a full-screen page with each section folded into a card. Tap a card to open it.

   Expand

2. Open Times. On a desktop it’s first in the sidebar and already open; on a phone, tap the Times card.

   Expand

3. Tap Date — it reads Select Date until you set it — and pick the day of the flight. The date is here on Times, not on General Info.
4. Under Block Times, tap Out (Blocks Off) and set the time you came off blocks. Then tap In (Blocks On) and set the time you went back on. Each one asks for a date first and then a time, which is how you log a leg that crosses midnight (→ C2).
5. Check Flight Time, under Totals. The app has filled it in for you: In minus Out, or Tach End minus Tach Start if you have no block times. You can type over it, but the app will ask you to confirm with Override Flight Time? — read C2 before you do.
6. Open General Info. Type the aircraft’s registration into Aircraft Registration and pick it from the list that appears. If it isn’t in the list, the app creates it when you save (→ C4).
7. Fill in Departure and Arrival the same way, picking each airport from the list. An airport the app doesn’t recognise is also created when you save.

   Expand

8. Tap Save — in the app bar on a phone, under the sidebar on a desktop. Nothing is kept until you do: leaving the form before then throws away what you typed.

You don’t have to go in this order. It’s one form with one Save — no Next, no Back, and nothing is checked section by section — so fill it in however suits you. Save checks the whole flight at once.

How to tell it worked

If the flight added anything new to your logbook — an aircraft, an airport, a person — a New Items Added dialog appears first: The following new items were added. You can edit them now or later. If it lists a new aircraft, tap Edit beside it to fill in its details while you’re here (→ C4). Otherwise tap Done.

Next, a short animation plays, showing the departure and arrival codes of the flight you saved.

Then you’re back on the logbook list, with your new flight at the top.

If something goes wrong

The same form, two shapes

The layout changes at 600 px of window width. On a phone held upright you get one shape; on a tablet or a desktop window, the other.

The fields are the same on both. Two section names differ (→ Reference below). On a phone, every card being folded up when the form opens is normal — nothing has been lost.

Editing a flight you already logged

Tap the flight’s card in the logbook to open its detail view, then tap Edit. You get the same form, titled Edit Flight, with everything filled in.

One difference: on an existing flight, the saved Flight Time is left as it is when the form opens. It’s only recalculated if you change one of the times (→ C2).

Getting your own hours onto the flight

Flight Time is the length of the leg. Your hours in a role — PIC, SIC, Dual Received — are separate fields on Operations. Put yourself on the crew list and the app fills them in for you:

1. Open Crew and tap Add Crew Member.
2. Tap Add Me (from Profile). Your own Directory entry fills the person field.
3. Pick a Capacity chip.
4. Tap Add to Flight.

The matching hours field on Operations gets the flight’s total:

Expand

For a role the chips don’t cover, use the small icon at the right of each hours field on Operations — its tooltip reads Copy Total Time (X). One tap puts the flight’s total into that field. The icon only appears once Flight Time has a number in it.

Every PIC total in the app counts your Student PIC hours as PIC time: the dashboard tile, Career Roles, and the totals for each aircraft, type and organisation. A leg with hours in both fields is counted once. The flight itself still shows the two fields as you entered them.

Adding other people to the crew doesn’t change your own hours. The app only fills in hours from the crew entry that’s you.

Which capacity a flight belongs in is a question for the rules, not the app. For Canada, see Logging flight time in Canada in the library; for the FAA, see How to log PIC time under FAA rules.

Reference: every section and what is on it

Nine sections. Two of them are labelled differently on a phone and on a desktop, so both names are given here. Only Times can’t be hidden.

On a desktop the nine sit in the sidebar with Cancel and Save beneath them. On a phone they’re nine cards down one page, and the back arrow in the app bar is the only way out without saving.

Times — headed Flight Times. Covered in full in C2.

General Info — headed General Information.

Crew — headed Flight Crew, Add crew members for this flight. Empty until you add somebody: No crew added yet. Add Crew Member opens a dialog with Add Me (from Profile), a Search People… field, ten Capacity chips — PIC, SIC, P1US, Relief, F/E, Instructor, Student, Student PIC, Examiner, Observer — and Add to Flight. Full coverage in C4.

Operations — the hours buckets, in eight groups.

Logging a simulator or FTD session. Use the block headed Simulator / FTD session, in the Training group. It has two controls, and a third appears once a device class applies:

Hours without a class count as flight time, and the form warns you. If you type hours but leave the class on Not a simulator session, the block turns red: These hours will count as flight time. Choose a class and the red warning is replaced by a note, naming the class, of what will happen instead.

Once a class applies, a third control appears: Supervised. It applies whether you chose the class here or the aircraft’s type already carries one. The choices are Not recorded, Yes — a qualified supervisor was present, or No. Some currency rules only credit a device session when a qualified supervisor was present. No counts as the condition not being met; Not recorded still credits the session — so they’re not the same answer.

If the aircraft is already a simulator in your Hangar, leave both alone. When the aircraft’s type carries a device class, the session is already excluded, and the block tells you so instead of asking again (→ E4). Only set a class here if that particular session was flown in a different device.

Instrument (Simulated) isn’t affected by any of this. Hood time in a real aircraft is flight time, and always counts.

External Loads — Specific configuration for rotary wing external load operations.

Takeoffs and Approaches / Takeoffs & Approaches — every counter and the approach list. Covered in full in C5.

Remarks & Tags / Remarks.

Additional Fields — Your custom fields — imported and hand-made. Empty until you make one: No custom fields yet — create one below to track anything beyond the built-in fields. New Custom Field creates one, and a field given a unit shows as Label (unit). Custom fields are set up and managed in Area J (→ J7).

Duty, Schedule & Fuel — three groups, all optional. One thing to know: the fuel group is only saved when at least one fuel figure is filled in, so a Unit chosen on its own isn’t kept.

Gotchas

The amber “Verification Needed” box is not an error. It appears on Operations when your PIC, SIC and Dual Received hours add up to more than the flight’s total, and it names the overlap: PIC (1.0) + SIC (0.5) exceeds Total Time (1.2). A leg split between roles that adds up exactly — 1.0 hours of PIC and 0.2 of SIC on a 1.2-hour flight — doesn’t trigger it. You can’t dismiss the box, and it doesn’t stop you saving. Use it as a reason to check your numbers; if they’re right, leave them alone rather than changing correct data to make the box go away.

Hiding a section hides the field, not the data. Turning a section off in Profile Settings → Entry Form only removes the place to type. What your flights already hold is still there, and still exported and counted. So if a number you know is on a flight has nowhere to show on your form, its section is switched off.

The Date is on Times. Most people look for it on General Info first. It’s the first field in the Times section, above Block Times.

Cross Country is on General Info. It’s the one hours field that isn’t on Operations with the rest. It works like the others; it’s only in an unexpected place.

Save replaces lists; it doesn’t add to them. Crew, tags and approaches are saved exactly as the form shows them when you tap Save. Delete an approach and save, and it’s gone (→ C5).

Saving copies three things from the aircraft onto the flight: its type, its operator and its owner. The operator and owner stay as they were on the day you flew. Aircraft change hands, and a later sale or lease shouldn’t rewrite flights you’ve already logged. The type works the other way round: an aircraft doesn’t change type in real life, so if you change its type in the Hangar, every flight already logged in it changes too — along with the class and category those flights report (→ E3).

Worked example

A single leg on 11 May 2026: Calgary to Vancouver, off blocks at 18:05 Zulu, on blocks at 19:35 Zulu, in C-GABC, flown by you as pilot in command, one daytime landing.

Times

General Info

Crew — Add Crew Member → Add Me (from Profile) → Capacity PIC → Add to Flight.

Operations — PIC now reads 1.5. You didn’t type anything here.

Takeoffs & Approaches — Day Landings 1.

Save. The animation shows CYYC → CYVR, and the card at the top of your logbook reads 1.5 hours, PIC 1.5.

Now the same leg, same aircraft, same times — but you were the student. The only change is the capacity chip: Student instead of PIC.

Operations — Dual Received reads 1.5. PIC is empty.

One chip is the only difference, and it changes what the flight counts as: the first builds command time, the second builds training received. That’s the field to get right.