Traveler Trips

Traveler mode is designed for passengers and travel enthusiasts rather than pilots. Instead of pilot flight records, you can log trips using fields such as departure airport, arrival airport, airline, flight number, seat class, seat location, trip name, booking reference, date, notes, and public or private visibility. Those entries feed into your travel profile, stats, maps, badges, and social activity. This makes Traveler mode a cleaner fit if you want to remember routes and milestones without pretending a passenger trip is the same as a pilot logbook entry. If you mainly travel commercially and care about airports, airlines, countries, and journey history, this mode gives you the right language and structure for that experience.

To add a trip in Traveler mode, open the trip logging flow and start with the basics: your route, airline, date, and any identity details you want to keep with the journey. You can then add optional extras such as flight number, seat class, seat location, trip name, booking reference, notes, and visibility. This process is lighter than Pilot mode because it is designed for travel tracking rather than pilot recordkeeping. If you prefer not to share your trip socially, choose private visibility before saving. If you enjoy using FlightLeague as a travel diary, adding a clear trip name and a few notes can make later browsing much more enjoyable. Your saved trips then feed into maps, stats, and badges automatically.

Traveler mode includes a booking reference field because some users like keeping travel details together in one place. Whether you use it is entirely up to you. If the reference is still relevant to an active or sensitive booking, think carefully about your visibility settings before saving the trip. In general, private visibility is the safer choice for entries containing anything you would not want casually visible. If you simply want a memory log, you may decide not to store that field at all. The point of the feature is convenience, not pressure. A good rule is to include the booking reference only when it genuinely helps you and to keep the entry private whenever the detail feels personal or operationally sensitive.

Seat class and seat location are traveler-focused details that make your trip history more personal and more searchable later on. They can help you spot patterns in how you travel, compare experiences, and add a little more depth to your travel profile beyond just routes and airlines. This is not a pilot feature, so Pilot mode users will not use those fields in the same way. For frequent travelers, small details like window versus aisle preference or premium versus economy travel can become part of the story your stats and trip history tell over time. They are optional, so if you want a lighter logging experience you can keep things simple and only capture the fields you actually care about.

Traveler mode can turn your trip history into useful and enjoyable stats such as airlines used, airports visited, countries tracked, longest trip patterns, and broader travel trends. These summaries help transform a simple log into a richer travel picture over time. The exact look of those summaries may vary across dashboard, profile, and analytics surfaces, but the core idea is the same: your logged history becomes something visual and easier to explore. If you are just getting started, your stats may look light until you build a larger trip history. That is normal. The best way to improve the value of the stats is simply to log journeys consistently and use clean route and airline information wherever possible.

Yes. Traveler mode still includes map-based experiences, because route history and airport visualisation are a major part of the product for both user types. The difference is that traveler maps reflect passenger journeys and travel history, while Pilot mode maps reflect pilot logs. Over time, your trips can contribute to a fuller picture of where you have been, which airports you use most, and how your travel footprint grows. If your map looks empty or incomplete, it usually means you do not have many saved trips yet or some entries need more complete route information. The map becomes more satisfying as you log consistently, especially when you include clear departure and arrival airport details.

A public trip can be visible in social areas of FlightLeague, depending on how the app presents activity in feeds and profiles. A private trip stays for your own records, stats, and maps without being part of that broader social surface. This works in the same overall way as pilot flight visibility, but it applies to Traveler mode entries instead. If you log trips for memory and personal stats only, private visibility is often the most comfortable default. If you enjoy sharing routes, milestones, or travel history with friends, public visibility can make the app feel more social. Because trip details can sometimes contain personal context, it is worth checking visibility before saving rather than assuming every entry should be public automatically.

Yes, and that is intentional. Traveler mode has its own identity across the dashboard, profile, maps, and social areas so it feels natural for passengers and travel enthusiasts rather than like a stripped-back pilot experience. Your stats, labels, and summaries are shaped around trips, airlines, airports, and travel patterns instead of pilot hours, landings, and training. The shared FlightLeague design language stays consistent, but the content of the experience changes to suit the role you selected. This distinction helps keep the app coherent for both audiences. If you chose Traveler mode and the app feels travel-focused rather than training- or logbook-focused, that is a sign the profile identity is working the way it should.