More Than a Logbook: How I Use PilotFlows PRO+ as an Airline Pilot

A logbook should do more than record where you've flown

As a pilot, I've always believed that a logbook should be able to do more than simply store flight entries.

Recording departure and arrival times is essential, but it is only one part of a pilot's workflow. Before a flight, there is a lot to consider. Weather, NOTAMs, routes, alternates, and the operational picture all play a role in understanding the flight ahead.

That got us thinking: what if your logbook could help you get more out of the information surrounding your flights, too?

This is where the idea behind PilotFlows PRO+ came from.

In September 2026, we introduced PRO+, a major step in our vision for a more capable pilot logbook. We wanted to give pilots access to additional tools that make their everyday workflow more convenient, help them explore their flying history, and bring relevant flight information together in one place.

Rather than treating the logbook as a destination where information is entered after landing, we wanted to make it useful throughout the flying journey.

Let me take you through my personal workflow as an airline pilot.

1. Importing my monthly roster

Every month, I receive my airline roster. Instead of manually entering every flight into my logbook, I can simply share the roster PDF with PilotFlows and import it.

That's it.

PilotFlows processes the roster, and my upcoming flights appear as drafts in the scheduled roster section. Flights taking place within the next 24 hours are also highlighted in the next-flights section, making it easy to see what's coming up.

This gives me a convenient overview of my upcoming flying and saves me from having to enter every flight individually before it even happens.

What if my airline uses a different roster format?

No worries. If your format isn't supported yet, get in touch with us. We can assess the format and work towards integrating it, potentially within just a few days, depending on its complexity.

We want PilotFlows to fit the way pilots actually work, rather than forcing everyone into the same workflow.

See the accompanying screenshot of the scheduled roster and next-flights sections.

2. Exploring my previous routes with Tracks

Once I've selected a flight, one of the first features I like to explore is Tracks.

This is one of those features that becomes more useful the more you fly.

Tracks overlays previous flights between the same departure and destination airports. Where ADS-B track data is available, I can also compare the actual routes flown.

This gives me a visual overview of how a particular route has been operated on previous occasions.

Have I typically flown close to the great-circle route? Have there been noticeable deviations? Have previous flights followed different routing patterns?

Being able to see those differences on a map is a great way to explore my own flying history and build a better understanding of the routes I regularly operate.

Of course, actual tracks can differ for many reasons, including weather, air traffic control instructions, airspace restrictions, and operational requirements. Previous flights are useful for context, not a prediction of what the next flight will do.

And the more flights I record, the more useful this personal history becomes.

3. Getting a broader weather picture

Next, I can open the weather map.

Instead of jumping between several different views just to get an overview, I can explore a map that brings together a range of relevant weather and aviation information.

Depending on the data available, this includes:

• SIGMETs and AIRMETs
• Weather radar imagery
• North Atlantic Tracks (NAT HLA information)
• Airport weather information
• Additional information relevant to the route and surrounding airspace

The map also highlights larger airports within a defined distance of the predicted great-circle route. This helps me explore the wider geographical picture and identify airports I may want to look at more closely.

For example, when reviewing a route across an area with potentially significant weather, I can quickly see which airports are situated along or near the route and investigate their conditions.

This is particularly useful for situational awareness. It helps me understand the broader environment around a flight instead of looking at each piece of information in isolation.

Exploring individual airports

The map is interactive, too.

When I select an airport, I can access available information such as METARs, TAFs, ATIS where available, wind components, and other airport-related weather data.

That makes it easier to explore individual airports without constantly switching between different screens.

Whether I want to look at the destination, review an airport along the route, or simply understand the weather situation in a particular region, having this information accessible on a map makes the process more intuitive.

4. Making NOTAMs easier to understand

NOTAMs are another important part of my pre-flight review.

Depending on the flight, there can be a substantial amount of information to go through. Filtering that information to focus on the relevant airports, airspace, and time period can make the process more manageable.

PilotFlows includes tools to filter NOTAMs and narrow down the information I want to review.

One particularly useful feature is the NOTAM map.

NOTAM coordinates and descriptions can sometimes be difficult to interpret when reading through a long list of notices. By visualising relevant NOTAMs geographically, I can get a clearer idea of where the affected areas or facilities are located.

This adds another layer of situational awareness and helps me understand the geographical context of the information I'm reviewing.

Rather than looking at coordinates in isolation, I can see how the affected areas relate to airports, routes, and surrounding airspace.

The map complements the textual information; it doesn't replace reading and understanding the applicable NOTAMs themselves.

5. Managing alternates and airspace along the route

Another useful part of my workflow is reviewing potential alternate airports.

Within a flight, I can add multiple alternates and assign tags to distinguish their intended roles, such as destination, take-off, or en-route alternates.

This helps me organise the airports associated with a flight and keep the information structured.

PilotFlows can also help me review standard alternates that I have used previously. I can look at those airports, check the available information, and consider whether I need to investigate other options.

The goal is to make the information easier to organise and review, not to automatically determine which alternate is suitable for a particular flight.

I can also plot the FIRs that my route crosses and explore the associated NOTAMs. This provides a more geographical way of looking at the airspace involved in a flight and the information that may be relevant to it.

Taken together, these features help me build a broader picture of the route before heading to work.

6. From a scheduled flight to a completed logbook entry

Once I've reviewed the flight and I'm ready to record it, the workflow is straightforward.

Because the flight already exists as a draft from my imported roster, I don't need to create a completely new logbook entry from scratch.

I simply fill in the relevant flight details as they become available.

After departure, I can enter the departure time and other applicable information. Once the flight is complete, I add the arrival time and any remaining details. If I've taken a nice picture during the trip, I can attach it to the entry as well.

And that's it: my flight is logged.

The idea is simple. Start with the information I already have, keep the flight organised while it is upcoming, and complete the logbook entry with the actual details once the flight has taken place.

Less repetitive data entry. A clearer overview of upcoming flights. And a more useful record of my flying history.

7. Why we're building PRO+

For us, PRO+ represents a broader idea about what a modern pilot logbook can be.

We don't want to stop at recording flight hours. We want to explore how a logbook can connect a pilot's schedule, personal flying history, and useful aviation information in a way that makes everyday tasks more convenient.

Tracks, weather visualisation, NOTAM mapping, roster imports, and alternate management are all examples of that philosophy.

Each feature addresses a practical part of the workflow. Together, they help make PilotFlows more than a place to enter flight times after a trip.

And we're not finished.

We're continuously improving the experience, working on new features, and listening to the pilots who use PilotFlows. Their feedback helps us understand what matters most and where we should focus our efforts next.

Our goal is to build a logbook that pilots genuinely enjoy using, whether they're building hours in a flying club, flying professionally, or working towards their next aviation milestone.

An important note about flight planning

PilotFlows PRO+ is designed to support your personal aviation workflow and provide tools for exploring flight-related information. It is not intended to replace official flight planning, operational flight preparation, or the procedures established by your airline or operator.

In my own work as an airline pilot, I use the planning tools and crew tablet provided by my airline for actual operational flight planning. Official and authoritative sources, current operational information, and applicable company procedures must always take precedence.

The features described here are intended to complement that workflow, provide additional context, and help manage my personal logbook.

More than logging. A better pilot workflow.

PilotFlows started with a simple idea: a pilot logbook could do more.

PRO+ is our next step towards making that idea a reality.

From importing my monthly roster to exploring previous tracks, viewing weather information, mapping NOTAMs, organising alternates, and completing my flight entries, I want PilotFlows to be a useful companion throughout my flying journey.

We're building it one feature at a time, guided by real pilot workflows and feedback from our growing community.

Because your logbook should do more than remember where you've been. It should help you get more out of every flight.