Pilot Logbook

Pilot mode is built as a digital flight logbook, so you can log much more than just a departure and arrival. A typical entry can include airports, aircraft type, aircraft registration, flight duration, night hours, distance, category, date, notes, landings, instrument approaches, holds, pilot function, cross-country status, actual instrument time, simulated instrument time, and visibility. That makes it useful for both everyday flying and more structured training or currency awareness. The exact fields are designed for pilot records, so Traveler mode does not use the same logging structure. If you are a student pilot, you can start simple and add more detailed fields as your confidence grows rather than feeling you must complete every field perfectly from day one.

To add a flight manually, open the pilot logging flow, enter the core route and aircraft details, then fill in the operational fields that matter for that flight. At minimum, most users start with departure airport, arrival airport, aircraft type, date, and duration, then add landings, instrument details, notes, and visibility. Airport and aircraft suggestions can help speed things up while reducing typing. If you are on the free tier, manual logging may be limited by monthly volume, but you can still use the feature to get started. Pro expands that limit for users who log frequently. If you are unsure what a field means, it is usually better to save an accurate partial entry than to guess and create a misleading record.

Suggestions are there to make logging faster and more consistent. In Pilot mode, airport validation helps reduce mistakes in codes or names, while aircraft suggestions make it easier to reuse common aircraft details without retyping everything every time. This is especially useful if you fly from the same airports often or regularly log the same aircraft types or registrations. It also improves route maps, stats, and analytics because the app can work better with cleaner, more standardised data. If a suggestion does not appear, it may simply mean the code is incomplete or the entry is not recognised yet. In that case, double-check spelling and airport format before assuming something is broken.

FlightLeague can estimate some values such as distance between airports, and in some flows it may help with time-related guidance too. These estimates are designed to speed up entry and give you a useful starting point, especially when you are adding a flight quickly. They are not a substitute for your own accurate record, so it is still worth checking the details before saving. This matters most in Pilot mode because logged flight data can feed into stats, maps, training context, and currency awareness. If an estimate looks off, it does not necessarily mean the app is wrong in a serious way. Airport selections, route assumptions, or incomplete fields can all affect what estimate is shown.

Yes. FlightLeague lets pilot users edit saved flights and delete them when needed. Editing is useful if you saved a quick draft and later want to add more detail, fix a registration, correct hours, or adjust visibility. Deletion is there for true mistakes, duplicates, or entries you no longer want in your logbook. Because flights can affect maps, analytics, badges, and social visibility, it is a good idea to review a change after saving to make sure everything still looks right. If you delete an entry that was public, it should no longer remain visible in the same way. If you are unsure, choose edit first before deleting so you do not remove something you actually wanted to keep.

A public flight can appear as part of your visible activity in social areas, depending on how the app surfaces feed content and profile activity. A private flight stays out of public view and is mainly there for your own logging, records, and stats. This matters only in Pilot mode because Traveler mode uses trip visibility instead. Public does not mean every detail will always be broadcast in the same way everywhere, but it does mean the entry is eligible for broader in-app visibility. Private is the better choice when you want the benefits of tracking without sharing the activity socially. If you care about consistency, set your default flight visibility in settings so new entries follow your preference automatically.

Yes. Pilot mode supports flight photos and shareable flight cards so your logged activity can also become something more visual and social when you want it to. Photos can add context to a memorable route or milestone, while shareable cards make it easier to present a flight in a cleaner, more designed format. These features are especially useful if you enjoy the community side of FlightLeague, but they are not required for keeping a solid digital logbook. If a card is shared from a private flight, review the visibility implications carefully and make sure the underlying entry is set the way you want. The safest habit is to check visibility first, then create or share the card.

AI logbook scan lets Pilot mode users upload an image of a logbook record and have FlightLeague help turn it into structured flight data. It is designed to save time when you do not want to type everything manually, especially for historical entries. After the scan, you should still review the result before saving, because handwriting, image quality, unfamiliar abbreviations, or unusual airport references can affect what is extracted. On the free tier, AI scan usage may be limited monthly. Pro expands access for users who rely on it more heavily. Think of AI scan as a speed tool rather than a blind auto-fill. It works best when the source image is clear, well lit, and easy to read.

Warnings usually mean the scan found something that looked incomplete, unclear, or unfamiliar rather than fully reliable. Common reasons include handwriting that is hard to read, partial airport codes, unusual shorthand, missing values, or an airport code the app could not confidently match. This is actually helpful, because it stops a questionable scan from looking more certain than it really is. In Pilot mode, those warnings give you a chance to review and correct the entry before it becomes part of your logbook, analytics, or maps. The best fix is usually to check the fields one by one and confirm the route, aircraft, and times manually. A clearer source image can also improve results on the next attempt.

The currency widget is a pilot-focused awareness tool that helps you keep an eye on relevant recency and activity patterns inside FlightLeague. It is not there to create stress. Instead, it gives you a quick view of whether your recent logged activity is keeping pace with the sort of recency picture you want to monitor. Because it is tied to Pilot mode, Traveler users will not see the same widget. The most important thing is to treat it as a practical visibility tool built from your logged data, not as a substitute for your own formal responsibility to keep accurate records. If the widget looks off, the first thing to check is whether your recent entries were logged completely and with the correct dates.

Yes. FlightLeague supports plain CSV, signed CSV, and signed PDF export tools for pilot logbook data in relevant contexts. Plain CSV is useful for spreadsheet backups, signed CSV keeps spreadsheet-friendly data tied to row fingerprints and a verification URL, and signed PDF is better for a formatted logbook presentation. Some export access is Pro-gated, especially where unlimited or more advanced export use is involved, but the feature is designed to feel practical rather than hidden. Before exporting, check that your entries are complete and accurate, since your output can only be as reliable as the data you have logged.