
FlightLog Analyzer
User Guide
A companion app for Microsoft Flight Simulator 2020 and 2024
Quick Start Guide............................................................................... 12
System Requirements........................................................................ 13
Flight Simulator 2024 Support............................................................ 13
Locating and Loading the Logbook.................................................... 14
Choose Logbook File(s).................................................................. 14
Picking the correct logbook file for each version........................ 15
Logbook Locator (Non-Standard Installations)............................... 15
Manually Load Logbook.................................................................. 15
The Main Display................................................................................ 15
Rich and Simple Views................................................................... 17
Activity Calendar............................................................................. 17
Filtering by Day........................................................................... 18
The Full Calendar........................................................................ 18
The Landing Log......................................................................... 20
Personal Records........................................................................ 21
Showing Those Flights................................................................ 22
What Counts................................................................................ 22
Landing Coach............................................................................ 22
Day and Night in Your Logbook...................................................... 27
What Counts as Night................................................................. 27
Night Takeoffs and Landings: Your Choice................................ 27
How It’s Worked Out................................................................... 28
Pilot Currency Uses the FAA Rule.............................................. 29
Pilot Currency................................................................................. 29
The Pilot Currency Window........................................................ 30
What the Logbook Can and Can’t Tell........................................ 31
Places Flown................................................................................... 32
What Counts as Flown There..................................................... 33
Airports the Database Doesn’t Know.......................................... 34
Showing Those Flights................................................................ 34
The Passport............................................................................... 35
Diverted and Returned Flights........................................................ 37
In the Grid.................................................................................... 37
Finding Them.............................................................................. 38
In Mission Debrief....................................................................... 38
What Counts................................................................................ 39
Highlighted Cells and Rows............................................................ 40
Logbook Utilization......................................................................... 41
Dark Mode....................................................................................... 42
Display Modifiers............................................................................. 42
Date and Time Formatting.......................................................... 42
Column Customization................................................................ 42
Editing Flight Records..................................................................... 42
Aircraft Registration..................................................................... 44
Naming an Airport....................................................................... 44
Lost-Flight Protection.......................................................................... 45
How Recovered Flights Are Displayed........................................... 45
Importing Lost Flights..................................................................... 46
Manual Entry Form...................................................................... 46
CSV Import.................................................................................. 46
Importing X-Plane Flights............................................................... 46
Decoding the X-Plane "Aircraft Name" Field.............................. 47
SimConnect Telemetry....................................................................... 47
Truncated Telemetry....................................................................... 48
Cleaning the Telemetry Data.......................................................... 48
Deleting Flights............................................................................... 48
Launch with Microsoft Flight Simulator.............................................. 48
Turning It On or Off......................................................................... 48
Running Next to the Clock.............................................................. 49
Only One Copy Runs...................................................................... 50
When a Flight Ends........................................................................ 50
Closing During a Flight................................................................... 50
Choosing Your Alerts...................................................................... 51
What You’ll Hear............................................................................. 53
What You’ll See.............................................................................. 53
On the Tablet View......................................................................... 54
For Friends Watching a Shared Flight............................................ 55
Charts and Graphs Panel................................................................... 55
Year in Review................................................................................ 55
What’s on the Page..................................................................... 57
Save as Image............................................................................ 58
Sharing a Link............................................................................. 58
Flight Postcard................................................................................ 59
Vertical Profiles Explained.................................................................. 61
What a Vertical Profile Is................................................................ 61
Top of Climb (TOC)........................................................................ 61
Top of Descent (TOD) and the 3° Path.......................................... 62
When the Route Is Too Short to Reach Cruise.............................. 62
Where the Numbers Come From................................................... 62
Terrain on the Profile...................................................................... 63
Safe Altitude.................................................................................... 63
Where the Terrain Comes From..................................................... 64
Off-Route Distance......................................................................... 65
The Vertical Scale........................................................................... 66
Collapsing the Profile Strip............................................................. 66
ATC View — Real-Time Flight Map................................................... 67
VATSIM Online ATC (Upcoming)................................................... 68
Hands-Free Radios and ATIS Weather (Upcoming).................. 71
Aircraft Position and Flight Path..................................................... 72
Color-By Modes........................................................................... 72
The HUD......................................................................................... 73
Waypoint Filter................................................................................ 74
The Altitude Profile Section............................................................ 75
Route (Vertical) or MSL / AGL: What’s the Difference?............. 75
A Second Line on the Profile...................................................... 76
Mouse Hover on the Profile........................................................ 76
The Route (Vertical) Profile............................................................ 76
Turning It On............................................................................... 77
Reading the Strip........................................................................ 77
The Summary Line...................................................................... 77
A Flight from Start to Finish........................................................ 78
Off-Route Warnings.................................................................... 78
When the Plan Is Below the Safe Altitude.................................. 79
Hovering the Route Profile.......................................................... 79
Messages You Might See........................................................... 79
Map Overlays — Aviation Charts................................................... 80
Destination Lines............................................................................ 81
Waypoint Sequencer...................................................................... 83
Automatic Destination Detection.................................................... 84
Other Controls................................................................................. 84
Snap to Overlay Zoom (F3)........................................................ 84
Zoom to Fit (F5)........................................................................... 85
Auto-Center (F4)......................................................................... 85
Destination Lines (F6)................................................................. 85
Clear Current Flight Tracks......................................................... 85
Nearest Airports (F7)...................................................................... 86
Reading the List.......................................................................... 86
Choosing Which Airports Count.................................................. 86
A Line to the Airport.................................................................... 86
Good to Know.............................................................................. 87
Measuring Distance (M).................................................................. 87
Step by Step................................................................................ 88
Reading It.................................................................................... 88
Day / Night Shading (Ctrl+F11)...................................................... 89
Reading the Map......................................................................... 90
Good to Know.............................................................................. 91
Top of Descent Alert....................................................................... 91
Setting It Up................................................................................. 92
What You’ll See and Hear........................................................... 92
On a Tablet.................................................................................. 92
Tablet View..................................................................................... 93
Turning It On............................................................................... 93
On the Tablet............................................................................... 94
Good to Know.............................................................................. 95
Share Live Flight............................................................................. 96
Starting to Share......................................................................... 96
What Your Friends See............................................................... 97
Good to Know.............................................................................. 98
Airport Heat Map................................................................................ 99
Navigation Database........................................................................ 101
The Vertical Profile Strip............................................................... 117
Reading It.................................................................................. 117
It Updates as You Plan............................................................. 118
TOC and TOD on the Map........................................................ 118
Hovering the Profile................................................................... 118
Routes Between High Airports.................................................. 118
Map-Clicked Endpoints............................................................. 119
When No Plan Line Is Drawn.................................................... 119
Folding the Strip........................................................................ 119
Auto VOR Route........................................................................... 119
What It Does.............................................................................. 119
How Far a VOR Reaches......................................................... 120
Step by Step.............................................................................. 120
Example: Altitude Makes the Difference................................... 120
When No Route Is Found......................................................... 121
Auto Procedures........................................................................... 121
Step by Step.............................................................................. 122
How It Chooses......................................................................... 122
Transitions................................................................................. 123
Too Far Out of the Way............................................................. 123
Choosing the Approach............................................................. 123
Example: Atlanta to Orlando..................................................... 124
Suggestions in the Pickers........................................................ 124
Buttons Only When They Apply................................................ 124
What It Can’t Know................................................................... 125
Messages You Might See......................................................... 125
Surprise Me................................................................................... 125
Step by Step.............................................................................. 126
Good to Know............................................................................ 128
Limits and Restrictions.............................................................. 128
Planning Aids................................................................................ 129
Cruising Altitude for Your Direction........................................... 129
Wind on the Runway................................................................. 129
Fuel Reserve............................................................................. 129
Copy Route............................................................................... 130
You’ve Flown This Before............................................................. 130
Which Flights Are Shown.......................................................... 131
Reading the Panel..................................................................... 131
The Tracks on the Map............................................................. 132
Folding the Panel...................................................................... 133
Fly It Again.................................................................................... 133
The Two Choices at a Glance................................................... 133
Starting It................................................................................... 134
The Planned Route................................................................... 134
How the SID, STAR and Approach Come Back....................... 135
Example: Phoenix to Las Vegas............................................... 135
The Route Actually Flown......................................................... 136
Which One Should I Use?......................................................... 137
Messages You Might See......................................................... 137
Mission Debrief — Historical Flight Replay...................................... 137
HUD Replay Mode........................................................................ 138
Waypoints in Replay..................................................................... 139
Map Overlays and Color-By Modes............................................. 140
Profile Scrubbing........................................................................... 140
Playing a Flight Back.................................................................... 140
Flight Events................................................................................. 140
Comparing Two Flights................................................................. 141
Flights With Telemetry: the Full Comparison............................ 143
Flights Without Telemetry: Map Only........................................ 143
Personal Bests on a Route........................................................... 143
Landing Reports............................................................................ 144
Reading the Markers................................................................. 145
What the Report Shows............................................................ 145
Comparing Your Landings on a Runway.................................. 146
Was the Approach Stabilized?.................................................. 147
Good to Know............................................................................ 149
Planned vs. Flown — the Route (Vertical) Profile........................ 149
The Debrief Summary............................................................... 149
Example: Reading a Debrief..................................................... 150
When the Flight Goes Past the Route — AFTER ROUTE....... 150
Older Flights.............................................................................. 151
Messages in Mission Debrief.................................................... 152
Multiple Debrief Windows............................................................. 152
Flight Map and Flight Profile for Historical Flights........................... 152
Flight Map..................................................................................... 153
Built-In Viewer........................................................................... 153
Google Earth Pro...................................................................... 154
Flight Profile.................................................................................. 155
Basic Use...................................................................................... 157
Type and Return........................................................................... 157
Partial Matches.......................................................................... 158
Excluding Instead of Including...................................................... 158
Clearing Individual Filters............................................................. 158
Filtering by Date............................................................................ 158
Group Analysis and Summarizing.................................................... 159
Drilling Into a Group...................................................................... 161
FlightLog Exporter............................................................................ 161
Export Format............................................................................... 162
Export Content.............................................................................. 162
Flight Numbers.............................................................................. 162
User Preferences.............................................................................. 162
Logbook Cleaner.............................................................................. 165
Choosing Which Flights to Delete................................................ 165
Restore Points.............................................................................. 166
Which Flights Are Eligible............................................................. 167
Choosing Which Flights to Correct............................................... 168
Restore Points.............................................................................. 168
Achievements Progress Tracker...................................................... 168
Logging In..................................................................................... 169
Steam Installations....................................................................... 170
FS2024 Achievements.................................................................. 170
Further Reading............................................................................ 170
Aircraft-Model Name Translation..................................................... 170
Example 1: Consolidating Variants.............................................. 171
Example 2: Replacing the Manufacturer Too............................... 171
Example 3: Wildcards................................................................... 171
Example 4: Regular Expressions................................................. 172
Auto-Archive and Manual Backups.................................................. 172
FlightLog Auto-Archive................................................................. 172
Manual Backups........................................................................... 172
Hot-Key Quick Access...................................................................... 173
Custom Colors.................................................................................. 174
Command-Line Interface (CLI)......................................................... 174
Running FlightLog Analyzer on Linux.............................................. 174
Step 1: Install Lutris...................................................................... 175
Step 2: Install FlightLog Analyzer................................................. 175
Step 3: Create a Symbolic Link to Your Logbook........................ 175
Step 4: Load the Logbook............................................................. 175
Instrument Approach Suffixes...................................................... 176
Vertical Profile and Route Terms.................................................. 176
Troubleshooting................................................................................ 178
Reverting to an Older Version of FlightLog Analyzer................... 178
Reverting to a Logbook Backup................................................... 178
Built-In Map Display Not Showing Satellite Overlay Correctly..... 178
A Popup Opens but Can’t Be Seen.............................................. 178
Finding Your Logbook in a Non-Standard FS Installation............ 178
The Program Crashes at Startup.................................................. 179
Automatically Send Logbook to Support.................................. 179
Manually Locating Your Logbook — Method 1......................... 179
Manually Locating Your Logbook — Method 2......................... 179
LNM (Little Navmap) Export Notes............................................... 179
SimToolKitPro Exports.................................................................. 180
Volanta Exports............................................................................. 180
Sky Dolly Export and Import......................................................... 181
Missing SIDs, STARs, or Approach Information.......................... 181
Missing Airport Name, City, or State............................................ 181
Viewing an Altitude Profile in Google Earth................................. 181
Reinstating "Show Again" Dialogs................................................ 182
Contact Information.......................................................................... 182
Registration / Licensing.................................................................... 182
Your License Key.......................................................................... 182
Anonymous Usage Counts........................................................... 183
Thank You for Supporting FlightLog Analyzer................................. 184
Appendix A: Loading a Flight Plan into MSFS 2024........................ 184
Step 1: Open the EFB................................................................... 184
Step 2: Open Flight Planner......................................................... 185
Step 3: Open the Route page....................................................... 186
Step 4: Start an import.................................................................. 187
Step 5: Choose Load PLN File..................................................... 188
Step 6: Load from this PC............................................................. 189
Step 7: Review the loaded route.................................................. 190
Step 8: Send the route to the aircraft........................................... 191
FlightLog Analyzer is a companion app for Microsoft Flight Simulator 2020 and 2024. It picks up where the in-game logbook leaves off — turning a flat list of flights into a searchable, sortable, filterable record of your time in the sim, with rich tools for visualizing where you flew and how.
Headline features include:
• Consolidated display of flights from FS2020, FS2024, or both at once
• Tabular logbook view with column customization, dark mode, and grid lines
• Filtering and grouping across virtually any flight attribute
• Flight path maps with smoothed and high-resolution telemetry tracks
• Altitude profiles charting climb, descent, speed, and elevation
• A real-time moving-map ATC View with HUD, IFR/VFR chart overlays, and waypoint navigation
• Mission Debrief — a full replay of any historical flight that recorded SimConnect telemetry
• Achievements tracker pulled live from your Xbox/Microsoft account
• Export to .CSV, .XML, .KML, Little Navmap, Volanta, SimToolKitPro, and Sky Dolly
FlightLog Analyzer also includes editing tools that act directly on Flight Simulator's logbook:
• Permanently remove unwanted flights with the Logbook Cleaner
• Restore missing takeoffs and landings with the Flight Fixer
• Automatic backups and restore points before every edit
If you just want to see what FlightLog Analyzer is all about, here's the short version:
1. Launch FlightLog Analyzer.
2. Let it scan for existing logbooks on your computer and confirm the selection.
3. All flights from the loaded logbooks appear in the main table — FS2020 and FS2024 are merged into a single list.
4. Click any column header to sort. Drag column headers to reorder. Right-click headers to hide columns.
5. Right-click any flight to see options: view the Flight Map, the Flight Profile, export, delete, fix missing takeoffs/landings, and more.
Right-click Fly It Again to load a flight into the Flight Planner — either the flight plan you flew it with, or the route you actually flew. See Fly It Again in the Flight Planner chapter.
6. Install a KML viewer if you want 3D maps — Google Earth Pro is recommended.
7. Click the Flight Group Analysis button to summarize your logbook by aircraft type, weather, year, or any other attribute.
8. Explore the Preferences menu to tailor the app to your workflow.
|
Tip: Tooltips are your friend. Hover over almost any button, label, or column header to see what it does. |
Microsoft Flight Simulator 2020 or 2024 must be installed on the same computer.
Beyond that, FlightLog Analyzer has no special hardware requirements. If Flight Simulator runs on your system, FlightLog Analyzer will too.
When you run setup.exe, Windows Defender may show a "Windows protected your PC" screen. This is not a virus warning — it appears for any executable that doesn't have widespread distribution history.
To proceed:
1. Click More Info.
2. Confirm the publisher shown on the next screen.
3. Click Run Anyway to continue the installation.
FlightLog Analyzer is fully compatible with Flight Simulator 2024. You can load one or both logbooks — FS2020, FS2024, or both at once — and all flights are merged into a single consolidated view.
When both are loaded, every operation (filtering, grouping, exporting, editing) works across both logbooks. Edits made through the Logbook Cleaner or Flight Fixer are applied to the correct file automatically.

One list for every sim: the FS Version column shows 2020 flights in amber, 2024 in cyan, and X-Plane in silver
|
Note: Flights are merged inside FlightLog Analyzer only — FS2020 continues to see only FS2020 flights, and FS2024 continues to see only FS2024 flights. The two sims are not aware of each other. |
To prevent you from losing flight history when you eventually uninstall FS2020, FlightLog Analyzer keeps an archived copy of every loaded logbook (see FlightLog Auto-Archive later in this guide).
FlightLog Analyzer offers three ways to find and load your logbooks, all under the File menu.
This is the default method and runs automatically the first time you launch the app. It performs a quick search in the standard installation directories for both FS2020 and FS2024 logbooks, then asks you to confirm which file belongs to which version.

Logbook selection dialog
When the scan completes, the results dialog appears. Use these clues to assign each file to the correct sim version:
• FS2020 (active) — the path typically contains the folder Microsoft.FlightSimulator_8wekyb3d8bbwe (highlighted in red in the dialog).
• FS2024 (active) — the path typically contains the folder Microsoft.Limitless_8wekyb3d8bbwe (highlighted in green).
• FS2020 (archived) — a previously saved copy of your FS2020 logbook, shown in blue. After you uninstall FS2020, this is the file you'll want to load to preserve your FS2020 flight history.
If you mis-identify a file, the only effect is that the FS Version column will display the wrong value. Run File → Choose Logbook File(s) again to correct it.
If you installed Flight Simulator into a non-default directory, the auto-scan won't find your logbook. Use this option to specify a starting folder and drill down from there. See the Troubleshooting section for tips on speeding up this search.
If you know exactly where your logbook is — or want to load a specific archived copy — use this option. It loads one logbook at a time and asks you to confirm which sim version it belongs to.
The Main Display is the heart of FlightLog Analyzer — every flight from your loaded logbooks appears here as one row in the table.
At startup, FlightLog Analyzer automatically locates Flight Simulator's logbook(s) and extracts the data for every flight. When both FS2020 and FS2024 are loaded, their flights are consolidated into a single view.

Main Display in Rich view — Activity Calendar, summary cards, and the redesigned toolbar
If you make new flights in the sim while FlightLog Analyzer is open, the logbook reloads automatically. You can also force a refresh from File → Refresh Display, or by pressing F5.
Hover over any column header to see a tooltip describing what that column shows.
|
Note: If the main display is empty, the logbook file likely couldn't be found at its default location — see Logbook Locator for Non-Standard FS Installations in the Troubleshooting section. |
The main grid has two looks. Rich is the default, and turns several columns into bars, colored dots, and small colored tags you can read at a glance instead of number by number. Simple is the classic plain grid, with nothing added. Switch between them any time with the Rich | Simple toggle in the toolbar’s top-right corner:

The Rich | Simple toggle, top-right corner of the toolbar
In Rich view:
• Flight Time, Day Flight Time, Night Flight Time, and Distance become bars, scaled to the busiest flights currently on screen.
• Take Offs, Landings, and their Day/Night breakdowns become colored dots — a blank cell means zero, so the flights with real activity stand out.
• Flight Simulator Version, Flight Rules, Flight End Status, Startup Location, Aircraft Type, Aircraft Class, AircraftCategory, Type of Flight, Weather, the runways, SID, STAR, and Approach all become small colored tags.
• Aircraft Manufacturer gets a colored dot next to its name.
The grid also switches to a darker background in Rich view, so the colors stand out more. Switching to Simple removes all of this — nothing is hidden or lost, it’s purely a different way of looking at the same data.
A compact heat-map strip above the filter panel shows roughly a year of flying activity at a glance — darker squares for busier days, the same idea as a familiar online code-contribution graph:

The Activity Calendar strip, above the filter panel
The FLIGHTS / TIME / DIST NM summary cards for FS2020, FS2024, and All sit to the calendar’s right — the same totals that used to live in the toolbar corner. Only fly one simulator version? The other one simply says so instead of leaving an empty space.
Hover any day to see its flight count and total flight time:

Hovering a day shows its flight count and flight time
Click a day to filter the main grid down to just that day’s flights. Ctrl-click adds another day to the selection, and Shift-click selects every flying day from the last-clicked day through the new one. Right-click the calendar for a one-click Reset that clears the selection and brings back the full list.

Selected days filtering the list down to just those flights
For the whole year at a glance — including your busiest day and your longest and current flying streaks — click the small button beside the calendar strip, or just double-click the strip itself:

The button that opens the full Activity Calendar

The full Activity Calendar
The full calendar works exactly the same way as the strip — click, Ctrl-click, Shift-click, and right-click to Reset — just with the whole year visible, and a period picker if you’d rather look at a specific year instead of the last 12 months.
When the filter panel is hiding some of your flights, both calendars still show your whole logbook: days with flights that pass the filter keep their colors, and days whose flights are all hidden by the filter turn gray. Rest the mouse on a gray day to see how many flights it has, and while some are hidden the full calendar’s legend adds a gray “Hidden by filter” box. An open calendar window follows the filter as you switch it on or off.

The full calendar with a filter on: one day passes the filter (teal), the rest of the year’s flying is gray.
How good was that landing, really? FlightLog Analyzer remembers every touchdown it recorded: the sink rate, the G, how far past the threshold you touched down, how far off the centerline, and whether the approach was stable. Watch your softest landing go up on the board, try to beat your smooth streak, and see in black and white whether you’re getting better. Butter or brick, you’ll know.
The LANDINGS card (with a small airplane touching down at its top right), between the Pilot Currency card and the Passport & Places card, keeps an eye on your landings. Last is your most recent touchdown’s sink rate and peak G, Best is your softest landing ever, and the bars along the bottom are your latest ten landings, oldest on the left and taller for harder. Green is Smooth or better (under 240 fpm), white Normal (240–400 fpm), amber Firm (400–600 fpm) and red Hard (600 fpm or more); the bars top out at 800 fpm, so anything harder is a full-height red bar — the same ratings as the landing reports in Mission Debrief. An amber pill beside the title, such as “3 diverted”, counts the flights that landed somewhere other than their flight plan’s destination (“2 returned” when none were diverted). Hover over it for both counts, and see Diverted and Returned Flights.

The Landings card: the last landing, the softest one ever, the latest ten, and the amber diversions pill.
Click the card to open the Landing Log (click it again to close it). The card shows for everyone; the window needs a Standard or PRO license once the trial period ends. It lists every landing FlightLog Analyzer has recorded, newest first — click any column heading to sort by it, and again to reverse:
• Date, Flight, Airport, Runway and Aircraft — where and in what. A touchdown off any known runway shows the flight’s destination and no runway. Runways are taken from the sim itself wherever it has described the airport (from 3.4.9.0 on), so an airport whose published runway data is off still gets its runway.
• Sink (fpm), G and Rating — the sim’s own sink rate and peak G at the moment of contact, and FlightLog Analyzer’s rating: Very smooth, Smooth, Normal, Firm, Hard or Very hard.
• Bounces — how many times it bounced back into the air before staying down; a bounce is part of the landing, not a landing of its own.
• Crosswind (kt) — the crosswind on the runway landed on, from the sim’s recorded wind (flights from 3.4.5.0 on).
• Stabilized by — 1,000 ft or 500 ft when the approach was stabilized by that height, No when it wasn’t, blank when there’s nothing to judge (see Was the Approach Stabilized?).
• Past threshold and Off centerline (ft) — where on the runway you touched down.
• Record — which of the records below that landing holds.

The Landing Log: the records across the top, two of them picked (the gold outlines), every landing below.
The tiles across the top of the window are your records:
• Softest — the lowest sink rate.
• Lowest G — the gentlest peak G.
• Most crosswind — the strongest crosswind you landed in, on a landing under 400 fpm that didn’t bounce.
• Best approach — stabilized the highest (by 1,000 ft beats by 500 ft), then the softest.
• Smooth streak — landings in a row under 240 fpm, counting back from your newest.
• Latest 10 — the average sink rate of your latest ten landings, and its rating.
Click a record’s tile to show that landing’s flight in the main window; a gold outline marks the tile. Click it again to bring all your flights back, or Ctrl-click more tiles to show several records at once. Pick an aircraft or an airport above the list and the records are worked out for just those landings — your best in one aircraft, or at your home field.
Click a landing to show its flight in the main window (Shift- or Ctrl-click to pick more, Ctrl+A for all of them). Double-click one to open that flight’s Mission Debrief, or right-click it for the same menu as the main window’s flight list: Mission Debrief, Flight Map (the Built-In Viewer or Google Earth), Flight Profile, Fly It Again and the rest. Close the Landing Log to bring all your flights back.
Only flights flown with FlightLog Analyzer running have their touchdowns recorded, so the log starts when you began recording telemetry; flights from before then aren’t in it.
A gear-up landing, a touchdown MSFS didn’t report (estimated), and a contact that can’t be a landing — dropped straight down at almost no ground speed, as when the sim places the aircraft, or lighter than 10 fpm, or under 1 G — stay in the list but never set a record. The card leaves out the ones that can’t be landings.
Stop guessing why your landings are firm. The Landing Coach finds the habit behind your hard ones, explains why it happens, and tells you exactly what to try on your next flight, all built from your own landings in your own aircraft. Most sim pilots never get a personal landing coach. Now you have one, waiting after every flight.
Only landings with telemetry can be coached: flights flown with FlightLog Analyzer running, so it recorded the touchdown and the approach. Landings from before you started recording, or flown without FlightLog Analyzer, aren’t in the Landing Log, and the coach can’t see them.
The Landing Coach looks at the landings in your Landing Log the way a flight instructor would. Instead of averages, it finds what your firm landings have in common, explains why that happens, and teaches you how to fix it, using your own numbers.
Open it with the Landing Coach button at the top of the Landing Log. A few sentences at the top sum up how your landings are going: the one thing that would help most, what to work on after that, and what’s already working for you.

The Landing Coach: the summary, then the one thing to work on first
Below that, each card is one thing to work on, the most important first (marked Start here). Every card has five parts:
• What I see in your landings — the evidence from your own landings, with the numbers.
• Why it happens — what’s going on with the aircraft or your technique.
• Try this — a few steps to fix it.
• Practice — a drill for your next few flights.
• Your goal for the next flight — a number you can check in the Landing Log afterwards.

Arrive at the flare with less descent: firm landings came in descending too fast below 500 ft

Slow down before the threshold: touching down faster than your own soft landings made them firmer

Build a routine so every landing is the same: the same numbers and cues every time

Know when your firm landings happen: every firm landing followed an approach that wasn’t stable

Land into the wind: tailwind landings came out firmer

Going well: the green cards say what’s already working

Good to know: facts about your landings that aren’t tips
Among the things it looks for: a missing flare (the nose lower on your firm landings than on your soft ones), descending too fast into the flare, carrying extra speed over the threshold, touching down in a crab or with a wing low, bounces and what causes them, approaches that weren’t stable at 1,000 ft, crosswind and tailwind landings, landing long or short, drifting to one side of the centerline, and an airport that keeps catching you out. Green cards are what’s going well.
It compares you with yourself, aircraft by aircraft, so a jet isn’t judged by a Cessna’s numbers, and it talks in airliner terms (the radio-altimeter callouts, thrust to idle at “retard”) when you fly jets. Pick one aircraft in its Aircraft list, or All aircraft; the Landing Log follows. The list shows only the aircraft with at least 5 landings the coach can use, because it takes that many to coach one aircraft on its own. Landings in your other aircraft still count under All aircraft. Untick Include steep approaches to leave out helicopter-style approaches; contacts of 2,000 fpm or more (crashes, or the sim putting the aircraft down) are left out unless you tick Include crashes. It needs at least 5 landings before it says anything, and at least 3 on each side of any comparison.
FlightLog Analyzer works out your night flight time, night takeoffs and night landings itself, from where the sun really was: at your aircraft’s position, by the sim’s clock. This section explains exactly what counts as night, the one choice you can make in Preferences, and how the numbers are worked out.
In aviation, night doesn’t start at sunset. The FAA (14 CFR 1.1), ICAO (Annex 1) and EASA all define night the same way: from the end of evening civil twilight to the beginning of morning civil twilight, the time when the center of the sun is more than 6° below the horizon. Between sunset and the end of civil twilight there’s still enough light to see the horizon and the ground, and pilots log that time as day.
• How long after sunset — around 30 to 40 minutes at the latitudes most of us fly. For example, at Bristol in mid-November the sun sets at about 16:20 UTC and civil twilight ends at about 16:58. It’s shorter near the equator and longer toward the poles.
• Summer near the poles — far north or south in midsummer the sun never gets 6° below the horizon, so there is no night at all, even though the sun sets.
• Night flight time — always uses this definition. The Night Flight Time column counts only the part of each flight flown after civil twilight ended in the evening, or before it began in the morning.
Real pilots don’t all keep their night takeoffs and landings the same way, so you can choose. In Preferences (F4), under General Flight Options, pick Night takeoffs and landings from:
• End of civil twilight (standard) — the default, and the standard for logging night with the FAA, ICAO and EASA. A takeoff or landing is a night one when it happens after civil twilight has ended, the same rule as night flight time. This is how ICAO and EASA pilots log them, and what the FAA counts toward a certificate (for example, the night takeoffs and landings a private pilot needs).
• 1 hour after sunset (FAA currency) — counts only the takeoffs and landings from one hour after sunset to one hour before sunrise. That’s the FAA’s separate rule for night currency (14 CFR 61.57(b)): to carry passengers at night you need three takeoffs and three full-stop landings in that window in the last 90 days. Some US pilots log only these, so their logbook shows exactly the landings they can use.
• Sunset — any takeoff or landing after sunset and before sunrise. This is how FlightLog Analyzer counted before version 3.5.4.0. It isn’t an aviation rule, but you can keep it if you’d like your numbers to stay as they were.

The three choices in Preferences, under General Flight Options.
An example at Bristol (EGGD) on 16 November, where the sun sets at 16:20 UTC, civil twilight ends at 16:58 and one hour after sunset is 17:20:
• A landing at 16:26 — day by civil twilight, day by the 1-hour rule, night by sunset.
• A landing at 17:05 — night by civil twilight, day by the 1-hour rule, night by sunset.
• A landing at 17:30 — night under all three.
When you change the setting, every flight’s day and night takeoffs and landings are sorted again by the new rule as soon as you close Preferences. Nothing is written to Flight Simulator’s logbook. A takeoff or landing count you set yourself in the grid keeps your number, and flights restored by Lost-Flight Protection keep the counts saved with them.
• By the sim’s clock — the sun is worked out for the time of day in the sim, not on your PC. If you set the sim to midnight, it’s night, even if it’s noon at home. With live time, it’s the real sun.
• Where you were at that moment — a takeoff is judged where and when the wheels left the ground, a landing where and when they touched down, and night time is added up along the route, minute by minute.
• With FlightLog Analyzer recording your flight — every recorded position is used, so night time is exact to the moment civil twilight ended where you were.
• From the logbook alone — the positions Flight Simulator recorded during the flight are used, together with the departure and destination airports, placed at the time you were actually in the air. Time on the ground before takeoff isn’t flight time, so a flight that waited an hour at the gate before a dusk departure is judged at the time it really flew.
• Day and night always add up — Day Flight Time plus Night Flight Time is always exactly the Flight Time.
• Why not Flight Simulator’s own day and night markers — the logbook carries markers for dawn, day, dusk and night, but they’re only written when the light changes and carried forward from there, so one missed marker leaves the wrong state for the rest of the flight. A November evening flight flown entirely in the dark could show as all day. The sun’s real position doesn’t have that problem, so the markers are used only for a flight with no position anywhere to work from.
The Pilot Currency card and window always use the FAA’s night-currency rule (one hour after sunset to one hour before sunrise), whatever you choose in Preferences, because currency is a legal test with one answer. So with the default setting, a landing 40 minutes after sunset counts as a night landing in your logbook but not toward night currency, exactly as it works for a real pilot. See Pilot Currency.
The ATC View’s day and night shading shows the same boundaries on the map: its second band begins where civil twilight ends, which is where night time starts. See Day / Night Shading.
Could you legally carry passengers today? A real pilot who hasn’t flown enough lately can’t, and FlightLog Analyzer holds you to the same rules. The Pilot Currency card tracks your day, night and instrument currency from your own logbook and turns amber before any of it runs out, so there’s always a reason for that next flight, and every flight counts.
Real pilots have to stay current: a few takeoffs and landings every 90 days to carry passengers, more of them at night to fly passengers after dark, and a handful of instrument approaches every six months to fly in the clouds. The PILOT CURRENCY card, between the Activity Calendar and the Landings card, keeps the same score for your sim flying, worked out from your logbook as of today:
• Day – 3 takeoffs and 3 landings in the last 90 days, at any time of day.
• Night – 3 takeoffs and 3 full-stop landings between one hour after sunset and one hour before sunrise, in the last 90 days. The sun is worked out for where you were and the time it was in the sim. This rule is fixed; your logbook’s night landings follow your own choice in Preferences (see Day and Night in Your Logbook).
• IFR – 6 instrument approaches in the last 6 calendar months. After that comes a 6-month grace period, in which a real pilot could still catch up with a safety pilot, before an instrument proficiency check would be needed.
Each line has a dot: green when you’re current, amber when it runs out within two weeks (or IFR is in its grace period), and red when it has lapsed. A current line shows the date it runs out; a lapsed one shows how far along you are, for example “1 of 3”.

The Pilot Currency card
Click the card to open the Pilot Currency window (click it again to close the window). The card shows for everyone; the window needs a Standard or PRO license once the trial period ends. For each of Day, Night and IFR it shows whether you’re current and until when, what the rule asks for and what you have now, and every flight that counts toward it today, with the date each one stops counting. Click a flight to show it in the main window; Shift-click or Ctrl-click picks more, and Ctrl+A picks a whole list. Double-click a flight to open its Mission Debrief, or right-click it for the same menu as the main window’s flight list: Mission Debrief, Flight Map (the Built-In Viewer or Google Earth), Flight Profile, Fly It Again and the rest. Close the window – with its Close button, Esc, or by clicking the card again – to bring every flight back.

The Pilot Currency window
Pilot Currency follows the FAA’s rules (14 CFR 61.57) as closely as the logbook allows. It’s for practice and fun, not a legal record, and a few things work a little differently:
• Touch-and-goes – count as takeoffs. MSFS often logs no takeoff after a touch-and-go, and some logbooks have no takeoffs logged at all, so every landing is taken to have had a takeoff before it.
• Full stops at night – the logbook doesn’t say whether a landing was a full stop or a touch-and-go. A flight’s last landing is always a full stop, so that one counts. When FlightLog Analyzer recorded the flight’s telemetry, every landing after which you slowed to taxi speed counts too. The Full stops from column says which was used.
• Approaches – an approach is whatever is in the flight’s Approach column: the one planned or assigned, or one you picked yourself. Nothing confirms it was flown to the end, and holding and course tracking, which a real pilot also needs, aren’t recorded at all.
• Aircraft – all aircraft count together. A real pilot’s currency is kept separately for each category and class of aircraft (and some types).
How much of the world have you really seen from the cockpit? Places Flown turns your logbook into a collection: every US state, every country and every airport you’ve flown to, counted up and stamped into your Passport. Fill in the blanks on the map, chase the states you’re still missing, and watch the numbers climb with every new adventure.
The purple PLACES FLOWN card, between the Landings card and the FS2020 / FS2024 cards, keeps score of everywhere you’ve flown: how many of the 50 US states, how many countries, and how many airports. It works from the logbook itself, so it covers every flight you’ve ever flown, not just the ones FlightLog Analyzer recorded.

The Passport & Places card

The Passport & Places card on the Main Display.
Click the card to open the Places Flown window (click it again to close the window). The card is named Passport & Places: the flags of your newest stamps sit beside its title, and a gold badge says NEW until you first open the window, then shows how many new stamps have arrived since you last did. The card shows for everyone; the window needs a Standard or PRO license once the trial period ends. It has three parts:
• Maps – six tabs: US States, Canada, Europe, S. America, Africa and Asia. Each one has a square for every state, province or country, laid out roughly where it sits on a real map. A place you’ve flown in is filled in, brighter the more flights it has; a gray one you haven’t flown in yet. Hover a square to see its name and its number of airports and flights. The tab’s score, such as “15 of 47 countries”, is to the right of the tabs, and the window opens on the tab where you’ve flown the most.
• Countries – every country you’ve flown in, with its number of airports and flights, the most airports first.
• Airports – every airport, with where it is, its Takeoffs, Landings and Other landings (see below), and the date of your first visit.

The Places Flown window
An airport counts when you took off from it or landed at it:
• The departure airport – always counts – every flight starts somewhere. It adds to the airport’s Takeoffs.
• The destination airport – counts only if the flight actually landed. A flight that ended in the air, or one you ended before you got there, doesn’t add its destination. It adds to the airport’s Landings.
• Landings along the way – count too. The logbook keeps the position of every landing in a flight, not just the last one, so a touch-and-go or a stop at another airport is credited to the nearest airport within 3 nautical miles of where you touched down. These add to that airport’s Other landings. The same goes for a flight that ended somewhere other than its planned destination: the airport you really landed at is counted.
• Off-airport landings – a landing with no airport within 3 nautical miles – a field, a lake, a crash – doesn’t add an airport. Heliports, balloonports and closed airports are never picked for a landing.
Example: you take off from Minneapolis, fly over to Wisconsin, do a touch-and-go at Eau Claire and land back in Minneapolis. Minnesota counts (the departure and the landing), and so does Wisconsin: Eau Claire shows one Other landing.
A state, province or country counts when any airport in it does. Its flight count is every flight that took off, landed or touched down there, and a flight with both ends in the same place counts once. The maps count the 50 US states, Canada’s 13 provinces and territories, 50 countries in Europe (Russia, Türkiye, Georgia, Armenia, Azerbaijan and Kosovo among them), the 12 countries of South America, the 54 of Africa and the other 42 of Asia. DC, the Faroe Islands, Gibraltar, French Guiana, the Falklands, Western Sahara, Palestine, Taiwan, Hong Kong and Macau have squares too, and the Countries list shows every country and territory, but those don’t add to a tab’s score.
Some airports have codes that exist only in the simulator or in add-on scenery – bush strips, custom fields, made-up codes such as T004. They’re in the Airports list as “(not in the airport database)” and count toward your airports, but FlightLog Analyzer can’t tell which state or country they’re in, so they don’t add to those. The line under the window’s title says how many there are. (To give one a name, see Naming an Airport.)
Click a square on the map, a country or an airport to show just its flights in the main window. Shift-click or Ctrl-click adds more – or takes out one you’ve already picked – so you can see, say, all your flights in Arizona, Utah and Nevada together. Right-click a country or an airport for the same menu as the main window’s flight list — Flight Map (the Built-In Viewer or Google Earth) maps all of its flights at once, and Export exports them; Mission Debrief, Flight Profile and Fly It Again need a place with just one flight. Picked squares get a violet outline. Picking in one part clears the other two, switching tabs drops the squares you picked, and the line at the bottom of the window says what’s shown.

Three states picked: their flights in the main window
Close the window – with its Close button, Esc, or by clicking the card again – to bring every flight back.
Click Passport at the top of the Places Flown window to open your passport: one stamp for every country in your logbook. Each stamp shows the country’s flag, the date of your first flight there, the airport that flight used and how many flights you have flown there. The stamps are tilted and inked in different colors, like the real thing.
A country is stamped as soon as you take off from it or land in it, by the same rules as the rest of Places Flown. The buttons above the stamps put them in order of First visit (the way a real passport fills up), A – Z, or Most flights. Rest the mouse on a stamp to see its flight and airport counts and the airports you have used most there. An airport that the airport database doesn’t know has no country, so it earns no stamp.

The Passport: a stamp for every country you have flown to or from.
You can also open it straight from the main window’s View menu: choose Passport. The menu item is grayed out when there are no flights to stamp yet, or when Places Flown isn’t available (it needs a Standard or PRO license, or the Trial Period).

View > Passport opens the Passport directly.
When a flight lands somewhere other than the destination in its flight plan, FlightLog Analyzer marks it. It compares the destination Flight Simulator kept from your flight plan (the Planned Destination Airport) with the airport the flight actually ended at (the To column). It works from the logbook itself, so it covers every flight you’ve ever flown, not just the ones FlightLog Analyzer recorded.
• Diverted – the flight landed at a different airport from the one the plan was going to.
• Returned – the flight landed back at the airport it took off from, when the plan was going somewhere else.
The To airport of a diverted or returned flight is shown in amber. In the Rich view a small amber arrow follows the code: ↪ for Diverted, ↩ for Returned. When the column is too narrow for the arrow, an amber corner mark takes its place. Hover over the To cell to see what happened, for example “Diverted: planned KLAS, landed at KTUS, 104 nm from KLAS”.

A diverted flight in the grid: the To airport in amber, with the reason in its tooltip.

A narrow To column: an amber corner mark instead of the arrow.
The Diverted / Returned filter, on the top row of the filter panel, shows only the diverted flights, only the returned ones, or hides them (uncheck the box to its left). It works like every other filter.

The Diverted / Returned filter set to Diverted: just the diverted flights are left in the grid.
The Landings card shows how many of your flights were diverted or returned: an amber pill beside its title, such as “3 diverted” (“2 returned” when none were diverted; hover over the card for both counts). The Landing Log’s summary line gives the same numbers and marks, in amber, the landing that ended each diverted flight. Year in Review lists the year’s diversions under Landings.
An amber “↪ Diverted to KTUS” (or “↩ Returned to KPHX”) badge sits on the airport the flight landed at. The flight plan’s destination stays on the map, dimmed, with a red “Planned KLAS” label, so you can see where you were going and where you ended up.

Mission Debrief of a diverted flight: where it landed, and where the plan was going.
A flight is only judged when there is something real to compare. These are left alone, never marked:
• No flight plan – a flight without a planned destination in the logbook. Flights flown with third-party ATC (SayIntentions, BeyondATC) often have none, for the same reason their SIDs and STARs are missing.
• No landing at an airport – a flight that never landed, ended in the air or away from an airport, or crashed.
• Missions – bush trips, careers, challenges and other missions. A bush trip’s plan names the trip’s last airport on every leg, so every leg would look diverted. Only free flights are judged.
• Very short flights – under 10 minutes. These are nearly always a restart a few minutes after the flight began, not a real return.
• A plan from somewhere else – a plan that doesn’t name a departure airport, or names a different one from the airport the flight took off from.
Two codes for the same airport count as the same airport: with or without the US “K” (KMIC and MIC), or two airports within 3 nautical miles of each other. An airport you only reached by diverting still counts in Places Flown and the Passport, since you really landed there.
FlightLog Analyzer uses color to flag special conditions in the logbook:
• Blue From/To airport cells — the flight departed or arrived near the listed airport rather than at it.
• Orange row — the record in Flight Simulator's logbook is corrupt (often the result of the sim crashing mid-flight).
• Yellow row — slewing was used during the flight.
• Amber To airport — the flight landed somewhere other than its flight plan’s destination (see Diverted and Returned Flights).
Click the Legend button on the main display for the full color key. The same information is available via tooltip on any colored cell or row.

Cell coloring legend
Flight Simulator's logbook file is capped at 64 MB. Asobo improved the compression in later updates, but the size limit remains — roughly 15,000 average flights. The pie charts on the main display show how full each logbook is: green for FS2020, blue for FS2024.

Logbook utilization pie charts
A dark theme is available for the main display and the Group Analysis display, which is easier on the eyes in dim lighting. Toggle it with F11, or via Edit → Toggle Dark Mode.
Horizontal and vertical grid lines can be enabled independently on the main and Group Analysis displays:
• Ctrl+F11 — toggle horizontal grid lines.
• Shift+F11 — toggle vertical grid lines.
Both options are also available from the Preferences menu.
The radio buttons on the left side of the display let you switch dates and times between 12-hour and 24-hour format, and between UTC (Zulu) and your local time.
To hide unneeded columns, right-click anywhere on the column headers and uncheck them. The Flight Number column cannot be hidden.
Click a column header to sort by that column; click again to reverse the sort order. Drag and drop column headers to reorder them.
Individual field values can be edited directly in the main grid, without leaving FlightLog Analyzer or touching Flight Simulator’s own logbook. The following fields are editable: Flight Rules, Type of Flight, Flight End Status, To/From, From Name/To Name, Takeoffs/Landings (Day/Night), Flight Time (Day/Night), Flight Distance, Manufacturer, Aircraft Model, Registration, Comment, Rwy - Depart, Rwy - Land, SID, STAR, Approach, Gate - Departure, and Weather.
Fields with a fixed set of valid values — Flight Rules, Type of Flight, Flight End Status, and the Takeoffs/Landings counts — edit through a dropdown:

Editing Flight Rules through its dropdown

Editing the Takeoffs count through its dropdown
Other fields — To/From, Manufacturer, Aircraft Model, Registration, Comment, Flight Time (Day/Night), and Flight Distance — are freeform text:

Editing the From airport as freeform text
Edits accumulate until saved. The toolbar’s save button reflects how many edits are pending, turning from a grayed-out No Changes state to a highlighted count once you’ve made at least one edit:

Pending edits — 3 Changes Pending

No unsaved edits
Rwy - Depart and Rwy - Land accept a runway number from 1 to 36, optionally followed by L, R, C, or W (e.g. “27” or “9L”) — leave the field blank to clear a runway that was never recorded.
SID and STAR accept any text and automatically capitalize it as you type, matching how these procedures are always published (e.g. “CANYN1”).
Approach uses a two-part editor: pick the approach type from a dropdown, then enter the runway in the box next to it, using the same format as Rwy - Depart/Rwy - Land plus an optional suffix letter (e.g. “27L” or “30-Y”).
The Registration column shows each flight’s aircraft registration (its tail number), the way a pilot’s logbook records it.
For flights FlightLog Analyzer recorded, it fills in by itself: the tail number set for the aircraft in Flight Simulator. Many aircraft come with a made-up default (such as ASXGS) unless you change it in the sim before the flight.
For older flights, or to correct one, click the Registration cell, type it (for example N172SP) and press Enter, then Save Changes. To go back to the recorded one, clear the cell and save.
Click the column header to sort by it. To include it in a CSV export, tick Only the grid’s columns, in the grid’s order in the Export window; the standard CSV keeps its columns as they are.
Many fields in the simulator — small strips, bush fields, gliding sites and add-on airports — use codes that no airport database knows: made-up codes such as T004 or BD7, unofficial national codes, or codes that the official lists have since given to a different field. FlightLog Analyzer can’t look up a name for these, so their From Name or To Name stays blank (or shows a different field’s name). You can name them yourself:
• Click the From Name or To Name cell of a flight, type the name — for example Muddy Lake for BD7 — and press Enter.
• It names the airport code, not just that one flight. Every flight from or to BD7 shows Muddy Lake at once, and so do the exports, the Airport Heat Map and the Flight Planner.
• Your name wins. If FlightLog Analyzer already shows a name for that code but it is the wrong field, the name you type replaces it.
• It’s saved straight away. Unlike the other edits, a name doesn’t wait for Save Changes and doesn’t change your logbook: it is kept in FlightLog Analyzer’s own file, MyAirportNames.txt.
• To go back to the built-in name, clear the cell (delete all its text) and press Enter.
• The flight needs a code to name. If its From or To is empty, enter the code in that column first.
A name is just a name: an airport whose position FlightLog Analyzer doesn’t know still won’t appear on the maps.
Edit > Edit My Airport Names ... (or Shift+F10) opens MyAirportNames.txt in your text editor (the file lives in %LocalAppData%\FlightLogAnalyzer). Each line is a code, a comma and a name; lines starting with # are notes. A new file already contains a few examples — real fields from the simulator whose codes the built-in data doesn’t know — so you have something to start from:
BD7,Muddy Lake
O77,Schurz Airport
NV47,Palomino Airport (Air Sailing Gliderport)
EDUE,Unterwössen Airfield
Keep the examples, change them, or delete them. Delete a line to remove a name, or add as many as you like at once. Save the file, then press F5 in FlightLog Analyzer to reload it.
Tip: The simulator logs every leg of a Bush Trip as departing from the trip’s first airport. To correct a leg, type the real departure code into its From cell — and if that field has no name, give it one in From Name.
|
Note: Flight record editing requires a PRO license once the trial period ends. |
Flight Simulator frequently drops flights from its logbook when subsequent flights are recorded. Once a flight is gone from the logbook file, it's gone for good — there's no way to retrieve it from within the sim. For anyone trying to keep their logbook accurate, this is endlessly frustrating.
FlightLog Analyzer addresses this with Lost-Flight Protection. Every time the app starts and reads the logbook, it records information about every flight it sees. If a flight that was previously present is missing on a later read, FlightLog Analyzer recreates that flight in its own display.
The flight remains missing from Flight Simulator's logbook file, but FlightLog Analyzer treats it as though it were still there — flight times, distances, airports, takeoffs and landings, telemetry, maps, and altitude profiles are all preserved and included in your summaries and statistics.
Recovered flights are color-coded by their flight number:
• Red flight number — a lost flight was recovered and SimConnect telemetry was captured for it.
• Violet flight number — a lost flight was recovered but no telemetry was captured.
• White flight number — the flight is still present in Flight Simulator's logbook (normal state).
You can add lost flights to FlightLog Analyzer through one of two methods: a manual entry form, or a CSV import.
Opens a simple dialog where you can recreate the basic attributes of a lost flight — date, time, airports, aircraft, duration. The flight is added to FlightLog Analyzer's internal lost-flight database and included in all statistics and summaries from then on.
This method covers basic flight attributes only.
For more detailed lost-flight records, use the CSV import. Two relevant menu options:
• Edit Import File — opens the template file in your text editor. The header section describes the three accepted formats in detail.
• Import Lost-Flight — reads the CSV file and adds its flights to FlightLog Analyzer's database.
The default file ships with 12 example entries. You can import the file as-is to see how the entries appear in your logbook, then right-click those flights and choose Delete Lost Flights to remove them. To disable an example without deleting it, prefix the line with
! — lines starting with ! are ignored by the importer.
The lost-flight import can also be used to bring in flights from X-Plane 11 or X-Plane 12. FlightLog Analyzer reads the X-Plane Pilot.txt logbook format directly.
X-Plane logbooks are far more limited than MSFS logbooks. The available fields are:
• Date (YYDDMM)
• Departure airport
• Destination airport
• Landings
• Total flight time (hrs)
• Night flight time (hrs)
• Aircraft name (may include manufacturer and/or model)
IFR time, cross-country time, and tail number are present in the X-Plane logbook but are not currently used. Most importantly, X-Plane does not record GPS track data, so flight paths cannot be plotted for X-Plane flights.
The lost-flight import defaults to %localappdata%\FlightLogAnalyzer\Data\LostFlightImports.txt. You can paste X-Plane logbook entries into this file, or simply select the X-Plane Pilot.txt file directly when prompted.
X-Plane stores manufacturer and model together in a single Aircraft Name field. By default, FlightLog Analyzer places the entire string into the Aircraft Model column. You can split it into separate manufacturer and model values using the Aircraft-Model Name Translation feature (described later in this guide).
Example translations:
"Cessna_172SP_G1000", "172 with G1000", "Cessna"
"Bombardier_CL_300", "CL 300", "Bombardier"
"Car_TBM850", "TBM 850", "Socata"
"Car_PC12", "PC-12", "Pilatus"
Flight Simulator exposes a real-time data feed through Microsoft's SimConnect API. FlightLog Analyzer subscribes to this feed and records the aircraft's state once per second — latitude, longitude, MSL and AGL altitude, true airspeed, ground speed, vertical speed, G-load, heading, and more.
Telemetry is what powers the high-resolution flight path on the map, the detailed altitude profile, and the entire Mission Debrief replay.
|
Note: Telemetry capture requires a PRO license once the trial period ends. |
To capture telemetry, FlightLog Analyzer must be running
throughout the entire flight — it sets up the SimConnect feed when Flight Simulator becomes active, and stops collecting when Flight Simulator closes. If FlightLog Analyzer isn't running while you fly, no telemetry is captured and the data is lost forever.
Start FlightLog Analyzer
before starting Flight Simulator. When the sim becomes active, you'll see Flight Simulator Connected in the status bar, followed shortly by Receiving Telemetry with a spinning asterisk that ticks with each data point recorded.
Or let Flight Simulator launch FlightLog Analyzer for you every time, so you never forget: see Launch with Microsoft Flight Simulator.
When the flight ends, the main display refreshes with the new entry. Flights that include telemetry are color-coded:
• Green — telemetry is captured and enabled.
• Gold — telemetry was captured but is currently disabled.
To toggle telemetry on or off for a flight, right-click it and select Disable Telemetry / Enable Telemetry. Disabling telemetry can be useful when you want to compare the sparse path stored in the FS logbook to the actual recorded telemetry path.
If FlightLog Analyzer wasn't running for the entire flight, part of the telemetry will be missing. The result is a track that ends (or starts) abruptly partway through the flight. Truncated-telemetry flights are color-coded on the main display (see the Legend) and start with telemetry disabled by default. You can still re-enable telemetry on these flights — it just won't cover the entire flight.
Telemetry can sometimes be captured outside the bounds of an actual flight — for example, while you're still on the menu screen or after the flight technically ended. If your telemetry database is taking up more disk space than you'd like, use
Edit → Clean "Flight Telemetry" Database to remove the extraneous data and shrink the file.
The telemetry database lives at %localappdata%\FlightLogAnalyzer\FlaTelemetry.db.
|
Important: When you delete a flight using the Logbook Cleaner, its telemetry data is permanently removed. Restoring an old logbook backup will not bring it back. |
FlightLog Analyzer records your flight (the telemetry behind the ATC View, Mission Debrief, Landing Analyses and Live Share) only while it’s running. The easiest way never to forget is to let Microsoft Flight Simulator launch it for you: every time you launch Flight Simulator, FlightLog Analyzer launches too, quietly next to the clock, and records the flight.
Note: Recording your flights needs a PRO license once the trial period ends. With a Standard license, the Mission Debrief and Landings windows say so, with an Upgrade to PRO button. Launching with Flight Simulator is only for recording, so a Standard license can’t turn it on in Preferences (it can turn off one the installer set), and if Flight Simulator launches FlightLog Analyzer anyway, it closes again straight away.
There are three ways:
• When you install or update — the installer has a box for it, ticked to begin with. Untick it to turn it off; each install remembers what you chose last time, and uninstalling FlightLog Analyzer turns it off.
• In Preferences — tick or untick Launch with Microsoft Flight Simulator (Edit → Preferences…). The change is made right away.
• Where you could use it — double-clicking a flight that has no recording, opening the Landings window before any landing was recorded, or opening the ATC View while Flight Simulator isn’t running. Say Yes, or click Record My Flights Automatically, and it’s on. These offers only appear while it’s off.

The installer’s box for launching FlightLog Analyzer with Microsoft Flight Simulator.
Behind the scenes, FlightLog Analyzer adds itself to Flight Simulator’s own list of programs to launch (a file called exe.xml), for every copy of MSFS 2020 and MSFS 2024 on your PC, Microsoft Store or Steam. Other add-ons in that list are left exactly as they are, and the file is backed up first (exe.xml.fla-backup).
When Flight Simulator launches it, FlightLog Analyzer doesn’t open its window over the sim: it goes straight to the system tray, the small icons next to the clock (click the ^ if you don’t see it). The first time, a Windows notice says it’s there. No splash screen, update reminder or announcement appears. The ATC View still opens by itself when your flight starts, if Auto Launch ATC View is ticked in Preferences.
Double-click the icon to open FlightLog Analyzer, or right-click it for Open FlightLog Analyzer, Open ATC View and Exit.

FlightLog Analyzer waiting next to the clock, with its right-click menu.
Minimizing it puts it back next to the clock. To have minimizing always go there, also when you launched FlightLog Analyzer yourself, tick Minimize to the Tray in Preferences (it’s off unless you tick it). It comes back as it was, so a maximized window comes back maximized. Closing the window with the X always closes FlightLog Analyzer.
FlightLog Analyzer only ever runs once. If it’s already running (next to the clock, say), clicking its taskbar, Start menu or desktop icon brings that copy to the front instead of opening a second one.
A few seconds after you end a flight, once Flight Simulator has added it to its logbook, the ATC View clears and the flight’s Mission Debrief opens by itself, with the ATC View minimized to make way for it. If you have more than one monitor, the debrief opens on one Flight Simulator isn’t using; on a single monitor it waits behind the sim until you switch to it. Flights with less than 2 minutes of actual flying are skipped.
To stop the debrief opening by itself, untick Auto-Open Mission Debrief After Flight in Preferences. You can always open any recorded flight’s debrief by double-clicking it.
If you close FlightLog Analyzer while your aircraft is moving or in the air, it asks first: the rest of the flight wouldn’t be recorded, and its track, Landing Analysis and Mission Debrief would stop where you closed it. Choose No to keep recording. Parked at the gate, it closes without asking.

Closing FlightLog Analyzer during a flight asks first.
While FlightLog Analyzer records your flight, it can tell you when something needs your attention: handy on a long leg left to the autopilot, or when you’ve stepped away from the screen. Each alert has its own sound, so you know which one it is without looking.
Note: Alerts work while FlightLog Analyzer is recording your flight: with a PRO license, or during the trial period.
Open View → Flight Alerts… (Shift+F6) and tick the ones you want:
• The autopilot disconnects in the air — when the autopilot goes from on to off while you’re flying, whether you switched it off or the aircraft did. It only counts once the autopilot has been on for 10 seconds, so switching it on and off while you set it up isn’t an alert. Off to begin with, because most aircraft already sound their own autopilot-disconnect warning.
• I’m within ___ nm from my destination — once per flight, when you come within that distance (in a straight line) of the destination in your flight plan. It needs a flight plan with a destination. Off to begin with.
• Wake-up chime, about ___ minutes before I arrive — once per flight, at your current ground speed (straight-line distance). On to begin with, set to 15 minutes, so you’re back at the controls in time for the descent.
• A flight worth sharing ends — after your smoothest landing yet, a new country, a milestone, a first visit to an airport or a butter landing, a note offers the flight’s Flight Postcard to share (see Flight Postcard). On to begin with, and it works with every license.
Below them, under On this PC, choose what this computer does: Play a sound, Show a note on the screen, or both. These two only change this PC: the ATC View’s banner and the Tablet View still show every alert you’ve ticked. So with both unticked, the alerts show only there (the window says so under the two boxes). To turn the alerts off altogether, untick all three alerts above. Try Them plays each alert once, a few seconds apart, so you know what to listen for. Save keeps your choices.

Choosing your alerts.
Like the chimes in an airliner’s cabin, each alert has its own sound:
• Autopilot disconnected — a fast high-low warble, six notes. The most urgent of them.
• Near your destination — two beeps on the same note.
• Wake-up chime — three notes going up.
• Top of descent — a falling pair of notes (ding-dong), and the pair twice when you reach the top of descent. This one is the ATC View’s own alert: see Top of Descent Alert.
A small note appears in the top-right corner of the monitor Flight Simulator is on, saying what happened (for example “Autopilot disconnected” or “About 15 minutes to KSEA”). It never takes the keyboard away from Flight Simulator, so your key presses keep going to the sim, and it closes by itself after 15 seconds, or when you click it.
The ATC View shows the same alert as a banner near its top (red for the autopilot) until you click it or a minute has passed.

An alert’s note on the sim’s screen, and its banner on the ATC View.
The destination alerts never go off at the start of a flight that begins close to its destination (a flight around the pattern, say): they wait until you’ve been further out than the distance or time you chose. Nothing goes off on the ground.
The Tablet View shows the same banners and plays the same sounds on the tablet or phone. A web browser only plays sound once you’ve touched the page, so while alerts are on, the Tablet View shows a button: Tap to hear the flight alerts on this tablet. Tap it once (or anywhere on the map). See Tablet View.
Someone watching your flight through Share Live Flight doesn’t get your alerts. They get two of their own: a note when you’re about 10 minutes from your destination (“Stay for the landing!”), so they can come back in time to watch you land, and another once you’ve landed. They hear them too, after one tap on the page (Tap to hear when they’re about to land). Opening the link late, or looking at an earlier flight, never sets them off for something that already happened. See Share Live Flight.
The main screen can also display a row of charts summarizing your flying — usage stats, totals by aircraft type, monthly hours, and more.
To expand or collapse the panel, click the small airplane icon at the bottom-left of the main display.

Charts and Graphs panel expanded
Interaction tips:
• Use the mouse wheel to zoom in and out.
• Hold Ctrl while dragging to pan when zoomed in.
• Click and drag with the left mouse button to "rubber band" zoom to a region.
• Right-click for additional options.
There are more chart summary types than will fit in the five chart slots. Right-click a chart and choose Change Chart… to pick which summary appears in that position. Use Reset This Chart… to return a slot to its default.
The Year in Review button, at the left of the Charts and Graphs panel, opens your year of flying on one page. It covers your whole logbook, not just the flights the filters show. The button names the year and turns gold in December and January; in January it opens on the year that just ended. The window needs a Standard or PRO license, or the trial.

The Year in Review button in the Charts and Graphs panel.

Year in Review: a year of flying on one page.
• Flight hours — with the change from the year before. For the current year, the hours you’re on pace for by December 31.
• Flights, distance and days flown — with your landings, how far around the world that distance would take you, and your longest streak of days in a row.
• Hours by month — your busiest month highlighted; the months still to come are outlined.
• Favorite aircraft — the top five by hours; Show all lists every aircraft you flew that year. Below them, how many were new to you.
• Places — the countries, US states and airports you flew to, how many airports were new, your home base (the airport you took off from and landed at most) and your most flown route (between two different airports, flown more than once).
• Landings — every landing in your logbook, day and night. The softest, the average sink rate, the share of stabilized approaches and the most crosswind come from the Landing Log, so they cover only the flights flown with FlightLog Analyzer running; the page says how many of the year’s flights that is.
• Records this year — the longest and the farthest flights, and the most flights and the most airports in a day.
• Badges — eight to earn each year: Century (100 hours), Frequent flyer (100 flights), Globetrotter (5 countries), Explorer (25 new airports), Night owl (10 hours at night), Iron butt (a flight of 5 hours or more), Butter (a landing under 60 fpm) and On a roll (7 days in a row). The ones still to earn are grayed out, with what they take.
Use the arrows beside the year, or the Left and Right arrow keys, to step through every year in your logbook. The current year is “so far”. Esc closes the window.
Save as image saves the whole page — not only the part that fits in the window — as a PNG picture, ready to post or attach to an email.
Share makes a link on flightloganalyzer.com that anyone can open in a web browser, phone included, so you can send your year to a friend. Type the name to show on it (or leave it blank) and click Make the link. Then:

Your link is ready: send it by email, copy it, open it, or take it down.
• Email — opens your email program with the link in a new message.
• Copy link — for Discord, a forum, or anywhere else.
• Open — see the page the way your friend will.
• Remove — takes the page off the website.
• Close — closes the box. The link keeps working until you remove it; click Share again any time to get it back.
Only the numbers on the page and the name you typed are shown; nothing else from your logbook is sent. Your license key goes with them, so sharing the same year again updates the same link instead of making a new one. Sharing a link needs a Standard or PRO license; Save as image works during the trial too.
Want to show off a flight? Right-click it in the logbook and choose Flight Postcard (a picture to share). FlightLog Analyzer makes a picture of that one flight, ready to paste into Discord, Reddit, a forum or an email.
Two more ways to get to it: the Share ▸ button on the playback bar of a flight’s Mission Debrief, and a note right after a flight worth showing off. When a recorded flight ends with your smoothest landing yet, a new country, a milestone (your 100th flight, say, or 500 hours), a first visit to an airport, or a butter landing under 100 fpm, a small note in the corner of the screen says so, with Share it: send a Flight Postcard. The note never takes the keyboard away from Flight Simulator and closes by itself; Don’t show these turns the notes off, and View > Flight Alerts turns them back on (A flight worth sharing ends).

The Share button on a Mission Debrief’s playback bar.

A Flight Postcard with its link ready to post: one click opens Reddit, Facebook, X or an email, already filled in.
What’s on it:
• The route — the track FlightLog Analyzer recorded, or the positions in Flight Simulator’s logbook. When there’s neither, a dashed straight line between the airports, and the postcard says so. Each end of the route is labelled with the airport it’s really at; a flight that started in the air (an air start), or whose recording stopped before it landed, has no label at that end, and the postcard says so.
• Where and when — the airports, the date (UTC or local, the same as the logbook) and the aircraft. When you have flown to the destination before, a small badge next to the route says which visit this is, counting this flight, like “12th visit to KMIC” (it shows from the second visit on; the first one gets the New Airport stamp).
• The numbers — flight time, distance, the highest altitude on a recorded flight, and night time when there was any (see Day and Night in Your Logbook).
• The landing — for a recorded flight, from the Landing Log: the sink rate and its rating, the runway and G, whether the approach was stabilized, and the crosswind.
• The stamp — the best thing about the flight, when there is one: your smoothest landing yet (once you have five or more landings to beat), a new country, a milestone flight or hours, a first visit to an airport (New Airport), or Butter! for a landing under 100 fpm.
• Your name — type it in Name on the postcard above the picture (a callsign works too), and your virtual airline if you fly for one. The postcard says Flown by, and FlightLog Analyzer remembers both for every postcard after it.
Copy picture puts it on the clipboard, so you can paste it straight in with Ctrl+V. Save picture saves it as a PNG file, 1200 × 630, the size Discord, Reddit and other sites show best. A small “Logged with FlightLog Analyzer” mark sits in the corner. Flight Postcards work with every license, and during the trial.
Above the postcard, choose Dark or Light, and Map: a real map (from OpenStreetMap) under the route. Untick Map for the plain background. Your choices stay for the next postcard.
Share link (Standard and PRO licenses) puts the postcard on flightloganalyzer.com and gives it its own link. Paste that link anywhere and the postcard shows up as the link’s preview picture. Or use the buttons under the link: Reddit, Facebook, X and Email open a new post in your own browser, already filled in with the link and a line about the flight — you look it over and post it with your own account. FlightLog Analyzer never asks for your passwords. Copy link copies the link, and Remove link takes the postcard off the website. Once a link is showing, changing the postcard (Dark or Light, Map, your name or virtual airline) updates the shared one by itself a moment later: the link stays the same, and the line under the buttons says when it is done. Tick Show this landing in Landing of the Week and the postcard can appear on flightloganalyzer.com/landings, the week’s softest landings that pilots shared.
Post to Discord sends the postcard straight to a Discord channel, with any license. The first time, paste the channel’s webhook link: in Discord, open the channel’s settings and choose Integrations > Webhooks > New Webhook > Copy Webhook URL (that needs the Manage Webhooks permission on the server, so ask its admin if you don’t have it). After that, one click posts. Tick Post my flights here by themselves and every flight FlightLog Analyzer records posts its postcard to that channel right after it ends — handy for a virtual airline or a group of friends who fly together.
Version 3.4.0.0 adds a side-on view of your route — a vertical profile — in three places: the ATC View while you fly, Mission Debrief after you land, and the Flight Planner before you take off. All three use the same ideas and the same arithmetic, so this chapter explains them once, with worked examples: Top of Climb, Top of Descent, the 3° descent path, terrain, safe altitude, and staying on your route. The chapters for each window then cover what is specific to that window.
If you have used Little Navmap, SimBrief, or the navigation display in an airliner, this will look familiar. If you have not, don’t worry — every term is explained below, and the Glossary at the end of this guide has a quick-reference list.
A map shows your route from above: where you are going. A vertical profile shows the same route from the side: how high you are along the way, and how high the ground is beneath you. Imagine slicing the landscape along your planned route like a loaf of bread and looking at the cut face — the ground runs along the bottom, your route stretches from the departure on the left to the destination on the right, and your altitude is drawn above it.
• Left to right is distance along the route — not time, and not a straight line between the two airports. If your route bends around a VOR, the profile follows that bend, so a point 300 nm across the profile is 300 nm along the route you are actually following.
• Bottom to top is altitude above mean sea level (MSL), in feet.
• Waypoints appear as thin vertical tick marks at the distance they sit along the route, with their names along the bottom edge. The departure and destination ticks are brighter than the rest.
Reading a profile comes down to two questions at any point along the route: how high am I (or will I be) here, and how high is the ground here?
Top of Climb is the point along the route where the climb ends and level cruise begins. Pilots plan it because it tells them how much of the route is spent climbing — and therefore how long until the aircraft settles into its efficient cruise speed and fuel burn.
FlightLog Analyzer works out TOC from three numbers: the departure airport’s field elevation, your cruise altitude, and a climb gradient — how many feet you gain for each nautical mile you fly forward.
The 300-feet-per-mile assumption — FlightLog Analyzer has no aircraft performance data, so it plans a climb of 300 feet for every nautical mile. That one number holds up surprisingly well across very different aircraft, because faster aircraft also climb faster:
|
Piston single |
500 fpm at 100 kt ground speed = 300 ft per nm |
|
Turboprop |
1,200 fpm at 240 kt ground speed = 300 ft per nm |
|
Airliner |
2,000 fpm at 400 kt ground speed = 300 ft per nm |
Worked example — Phoenix Sky Harbor (KPHX) sits at 1,135 ft. Climbing to a 12,500 ft cruise means gaining 12,500 − 1,135 = 11,365 ft. At 300 ft per nm that takes 11,365 ÷ 300 = 37.9 nm, so TOC is 37.9 nm after KPHX.
In the ATC View the estimate improves as you fly. Once you have been climbing for a little while, FlightLog Analyzer measures your actual climb gradient from the telemetry and uses that instead — so if your aircraft climbs more steeply than 300 ft per nm, TOC moves closer to the departure; more gently, it moves farther away. The moment you actually level off at cruise, the TOC marker moves to exactly where that happened. Until then it is labeled (est).
Top of Descent is where you need to leave your cruise altitude so that you arrive over the destination at a comfortable, steady descent rate. Start down too late and you end up high and fast, diving for the runway; start too early and you spend a long time low and slow, burning fuel and listening to the engines.
FlightLog Analyzer plans the descent on the standard 3° path — the same angle as most instrument approach glideslopes, and the basis of the classic “3-to-1” rule of thumb. A 3° path loses about 318 feet for every nautical mile flown, which is roughly 1,000 feet every 3 nm.
Worked example — Cruising at 12,500 ft into Las Vegas (KLAS, field elevation 2,181 ft), there is 12,500 − 2,181 = 10,319 ft to lose. At 318 ft per nm that takes 10,319 ÷ 318 = 32.4 nm, so TOD is 32.4 nm before KLAS.
An airliner example — From 35,000 ft into New York JFK (field elevation 13 ft): 34,987 ÷ 318 = 110.0 nm before the airport. An airline pilot’s mental shortcut — altitude in thousands × 3, so 35 × 3 = 105 nm — lands in almost the same place.
|
Tip: To actually fly a 3° path, set a descent rate of about five times your ground speed. At 90 kt that is about 475 fpm; at 120 kt about 635 fpm; at 250 kt about 1,325 fpm; at 450 kt about 2,385 fpm. (The exact figure is 318 ft per nm × ground speed ÷ 60.) |
On a short hop, the climb and the descent can meet before you ever reach the cruise altitude you planned. When that happens the profile draws a single peak where the two lines cross, labels it TOC/TOD, and the summary line says PEAK instead of CRUISE — that peak is the highest altitude the route can sensibly reach.
Example — Phoenix (KPHX) to Chandler (KCHD) is only about 14 nm. With 35,000 ft entered as the cruise altitude, a 300-ft-per-nm climb from KPHX and a 3° descent into KCHD meet about 7 nm out at roughly 3,400 ft — so that is what is drawn, and the summary reads “PEAK 3,367 ft (route too short to reach 35,000 ft)”.
• Cruise altitude — In the ATC View and Mission Debrief, it is the cruise altitude saved in the flight plan you loaded in MSFS, whether you built it in the World Map, imported it from SimBrief, or exported it from FlightLog Analyzer’s own Flight Planner. In the Flight Planner, it is the Cruise Alt (ft) box.
• Field elevations — From the airport database FlightLog Analyzer already uses for airport names, cities and coordinates.
• Departure point — The flight plan’s departure airport. If the plan doesn’t name a departure airport FlightLog Analyzer recognizes, the ATC View starts the route from the aircraft’s first reported position instead.
• The route itself — The departure, every waypoint in the flight plan in order, and the destination. Hiding waypoint types with the ATC View’s Waypoint Filter only hides their map markers; the profile always follows the full route.
• Terrain and safe altitude — From a free, worldwide terrain elevation dataset; see Where the Terrain Comes From below.
|
Note: Some flight plans that MSFS saves for VFR flights contain a tiny placeholder cruise altitude — 500 to 1,100 ft — that is below the airports themselves. Rather than draw a nonsensical plan, FlightLog Analyzer leaves the planned line out and says why in the summary (for example “plan cruise altitude 500 ft is below the airports”). Your flown altitude, the terrain and the off-route information are still shown. |
The brown area along the bottom of every profile is the ground. It comes from two places:
• Terrain along the planned route — the ground elevation along the whole planned route, from departure to destination, read from a worldwide terrain dataset (see Where the Terrain Comes From). This is what lets you see the mountains ahead of you before you get there. Ahead of the aircraft it is drawn as a lighter brown fill; over the part already flown it becomes a thin dashed outline, because there the ground that matters is the ground you actually flew over (next).
• Terrain flown over — in the ATC View and Mission Debrief, the ground directly beneath the aircraft as reported by the simulator itself (your altitude minus your height above the ground), recorded as you fly. It is drawn in solid brown on top of the route terrain, for the part of the flight already flown. If you wander off the route, this shows the ground you actually flew over rather than the ground on the planned line.
Example — A flight planned direct from Prescott (KPRC) to Cottonwood (P52) has the 7,800 ft Mingus Mountain ridge right on its planned line. A pilot who swings north around the ridge at 6,000 ft flies over ground at about 5,000 ft. On the profile, the solid brown under the green line is that 5,000 ft ground, and the ridge on the planned line appears only as a dashed outline above it — what the direct route would have crossed, not ground the aircraft flew through.
Where many points fall into the same sliver of the strip, the highest ground among them is drawn, so a narrow ridge is never averaged away.
A profile shows the ground right along the route’s centerline — but an aircraft is never exactly on the line, and a ridge a mile or two to the side matters just as much. That is what the safe altitude is for. For every leg of the route, FlightLog Analyzer works out a leg safe altitude:
|
Note: Leg safe altitude = the highest terrain within 4 nm either side of the leg, plus 1,000 ft, rounded up to the next 100 ft. |
On the profile each leg’s safe altitude is a red line, stepping up and down from leg to leg, with the highest one labeled — for example “SAFE 12,400”. The summary line shows the highest safe altitude on the whole route as SAFE ALT, and if your planned cruise altitude is below it, a red banner says so:
⚠ CRUISE BELOW SAFE ALTITUDE (12,400 ft)
Worked example — The Phoenix–Las Vegas route used throughout this chapter crosses the high country of Arizona and New Mexico. On its ADYAN–MAXXO leg the highest terrain within 4 nm is 11,339 ft, so that leg’s safe altitude is 11,339 + 1,000 = 12,339, rounded up to 12,400 ft. Every other leg is lower (the last one into KLAS is just 3,300 ft), so the route’s SAFE ALT is 12,400 ft — which is why the examples here use a 12,500 ft cruise. Plan the same route at 6,001 ft and the Flight Planner warns you straight away:

Phoenix–Las Vegas planned at 6,001 ft: the terrain (brown) rises well above the planned cruise line, and the red banner warns that the cruise altitude is below the 12,400 ft safe altitude.
Things to know about safe altitude:
• It is terrain only. Towers, buildings and other obstacles are not in the terrain data, which is one reason for the 1,000 ft margin. Real-world minimum altitudes for mountainous areas often use 2,000 ft — add your own margin when the terrain is rugged.
• It reads sharp peaks a little low. Each terrain sample covers roughly 250 m of ground (more on routes over 1,500 nm) and averages the elevation within it, so a broad mountain comes out within about 100 ft of its summit, but a needle-like peak can read several hundred feet low — the Matterhorn’s 14,692 ft summit reads about 13,900 ft. The 1,000 ft margin absorbs most of that, but on a route that passes close to a sharp peak, treat the margin as smaller than it looks.
• It is not an official minimum altitude. Charted minimums (MEA, MOCA, MORA, grid MORA) also account for obstacles, navigation signal coverage and airspace. Use SAFE ALT as a planning check, not a substitute for the charts.
• Climbing out and descending in, you will be below it. The warning is about your cruise altitude; it is normal for the climb out of the departure and the descent into the destination to pass below the safe altitude of the first and last legs.
Terrain elevations come from the free “Terrain Tiles” dataset on Amazon Web Services Open Data — a worldwide collection of public terrain data (originally assembled by Mapzen). FlightLog Analyzer downloads only the small pieces (“tiles”) that cover your route’s corridor, the first time a route needs them, and keeps them on your computer under %LocalAppData%\FlightLogAnalyzer\TerrainCache — terrain doesn’t change, so each piece is only ever downloaded once.
• Speed — a 1,000 nm route typically needs a couple of seconds the first time, and is near-instant after that. While it loads, the Flight Planner’s summary line shows “(terrain loading...)”; the ATC View simply adds the terrain when it arrives.
• Offline — without an internet connection, routes whose terrain isn’t already cached show “(terrain unavailable)” in the Flight Planner, and no route terrain or safe altitude in the ATC View. Everything else keeps working.
• Accuracy — about 150–300 m between samples. Spot-checked against published airport elevations: Phoenix 1,109 ft (published 1,135), Denver 5,384 ft (5,431), Aspen 7,762 ft (7,820).
The terrain data is public domain or openly licensed, and its providers require this attribution, which also appears in the corner of the maps (“Terrain: USGS, NOAA & others”):
|
United States |
3DEP (formerly NED) and global GMTED2010 and SRTM terrain data courtesy of the U.S. Geological Survey. |
|
Global |
ETOPO1 terrain data U.S. National Oceanic and Atmospheric Administration. |
|
Arctic |
ArcticDEM terrain data DEM(s) were created from DigitalGlobe, Inc., imagery and funded under NSF awards 1043681, 1559691, and 1542736. |
|
Australia |
Australia terrain data © Commonwealth of Australia (Geoscience Australia) 2017. |
|
Austria |
Austria terrain data © offene Daten Österreichs – Digitales Geländemodell (DGM) Österreich. |
|
Canada |
Canada terrain data contains information licensed under the Open Government Licence – Canada. |
|
Europe |
Europe terrain data produced using Copernicus data and information funded by the European Union - EU-DEM layers. |
|
Mexico |
Mexico terrain data source: INEGI, Continental relief, 2016. |
|
New Zealand |
New Zealand terrain data Copyright 2011 Crown copyright (c) Land Information New Zealand and the New Zealand Government (All rights reserved). |
|
Norway |
Norway terrain data © Kartverket. |
|
United Kingdom |
United Kingdom terrain data © Environment Agency copyright and/or database right 2015. All rights reserved. |
Off-route distance is how far the aircraft is to the side of the planned route, measured straight across to the nearest leg, in nautical miles. Pilots call this cross-track error.
• In the ATC View, the summary line adds OFF ROUTE and the distance whenever you are more than 1 nm to the side of the route.
• When you hover any part of the route you have flown — in the ATC View or Mission Debrief — the readout includes how far off route that point was, if it was half a mile or more.
• In Mission Debrief, the summary reports the largest deviation of the whole flight and how far along the route it happened.
Example — On a 19.5 nm hop from Prescott (KPRC) to Cottonwood (P52), a pilot detours north to sightsee past Clarkdale before turning back to land. The Mission Debrief summary reads MAX OFF ROUTE 6.0 nm (at 15.1 nm): the farthest the aircraft got from the planned straight line was 6.0 nm, 15.1 nm along the route. Hovering that spot on the profile puts a green dot on the map exactly where it happened.
The profile’s vertical scale does not start at sea level. It starts just below the lowest thing that matters on that flight — the lowest ground along the route or flown over, the airport elevations, or your own lowest altitude (but never below sea level unless the ground itself is) — and the range is printed on the strip as SCALE, for example “SCALE 4,700–14,400 ft”.
Here is why. Flying 1,500 ft above Colorado terrain that is itself at 5,000 ft, a scale starting at sea level would spend nearly 80% of the strip’s height on solid ground and squeeze the part you actually care about — your height above the terrain — into a thin sliver at the top. Starting the scale just below the ground spends the whole strip on the band you are flying in, so climbs, dips and the gap between you and the terrain are easy to see.
|
Note: Because the bottom of the strip is not always sea level, check the SCALE figures before comparing two different flights side by side — the same height on screen can mean different altitudes on each. |
Both profile strips — the one at the bottom of the ATC View and Mission Debrief, and the one under the Flight Planner’s map — have a PROFILE tab in their top-left corner, styled like the maps’ own MAP, HUD and WPT tabs. Click the tab, or anywhere on the strip’s top line, to fold the strip down to a single line and give the map more room; click again to bring it back. The arrow shows which way it will go: ▼ PROFILE folds it down, ▲ PROFILE opens it up. Your choice is remembered from one session to the next.
Folded, the strip still shows its summary line in Route (Vertical) mode — including SAFE ALT and, in red, any below-safe-altitude warning — so you can keep an eye on the countdown to your descent while the map has the whole window.
![]()
The ATC View profile strip folded down to its summary line with the PROFILE tab.
Fly with your own radar scope beside you. The ATC View is the big-picture moving map Flight Simulator never gave you: your airplane and its track painted across real aviation charts, the live numbers on a HUD, and an altitude profile that shows where you’re going, not just where you’ve been. Always know exactly where you are on the chart, see top of descent coming before it sneaks up on you, put the whole map on a tablet beside your yoke, and let friends and family watch you fly from anywhere in the world.
The ATC View is FlightLog Analyzer's real-time moving map. It tracks your aircraft as you fly, painting the flight path behind you in your choice of color modes and overlaying a HUD with live telemetry, an altitude profile along the bottom, and aviation chart overlays on top of a real-world map.
|
Note: The ATC View requires a PRO license once the trial period ends. |
To use the ATC View, FlightLog Analyzer must be running concurrently with FS2020/FS2024 and must be running for the entire flight to capture the complete telemetry stream.
With FlightLog Analyzer running, the ATC View automatically opens and centers itself on your aircraft the moment you select a flight location in the sim. If you close the window mid-flight, press F6 (or use View → ATC View – Real-Time Flight Map) to reopen it. The full flight path collected so far is retained.
ATC View showing the aircraft, flight track, HUD, altitude profile, and aviation chart overlay
Coming in a future version of FlightLog Analyzer — here’s a first look.

Fly on VATSIM and you’ll never have to wonder who’s out there again. The ATC View paints the live VATSIM network right onto your map: every center’s airspace, every staffed tower, approach and ground, every ATIS, all around your airplane as you fly. See at a glance whose airspace you’re in, who’s handling the airspace ahead, whether your destination has a tower and approach online, and the frequency to call before you get there. Real controllers, live, on the same map as your flight.
VATSIM is the free online network where real people work as air traffic controllers for sim pilots. Tick VATSIM ATC in MAP CONTROLS, and the map draws every controller who’s online right now:
• Center — a blue outline around each staffed center’s airspace, with its callsign inside (such as IND_20_CTR). Oceanic and other very large areas are outlined in magenta instead: VATSIM calls these FSS positions. They’re usually oceanic control, such as Shanwick or Gander Oceanic over the Atlantic, or a “top-down” position covering the upper airspace of several countries on busy event days. They often sit over or around ordinary centers, so the second color shows they’re a different layer, not one more center next door.
• Approach and departure — a dashed orange outline of the approach controller’s real airspace, such as SoCal Approach around San Diego; click anywhere inside it for the controller’s popup. Where no outline has been published for that approach, a dashed orange circle around the airport instead.
• Airports — a small dark badge for each staffed airport, with a colored chip for each position online: APP (approach), TWR (tower), GND (ground), DEL (delivery) and ATIS.

VATSIM ATC ticked in MAP CONTROLS, and the popup for the KLEX badge: the tower, its ATIS and the KSDF ATIS folded into it
An airport’s popup opens with its full name, such as KSAN · San Diego International Airport. Click a badge, an outline or a circle to see each controller’s frequency, how long they’ve been online and their information text, along with the full ATIS. When two airports’ badges would overlap, the busier airport keeps its badge and the other folds into it as a +1 chip; the popup lists both, and zooming in separates them.

Click a center’s outline to see who’s working it: here London’s LON_E_CTR and LON_D_CTR, with each controller’s frequency, rating, time online and notes

An approach controller online: SoCal Approach’s real airspace around San Diego outlined in dashed orange, and its popup from the KSAN badge (the controller’s name blurred)
MSFS doesn’t need to be running: the controllers come from VATSIM over the internet, so you can open the ATC View before a flight to see who’s on. The map refreshes them on its own about every 20 seconds while the ATC View is open, and the checkbox remembers whether you left it ticked. Your own aircraft and Traffic still come from the sim; flying on VATSIM, the Traffic you see is the other VATSIM pilots, as your pilot client shows them in MSFS. The controllers also show on the Tablet View.
The credit line in the map’s bottom-right corner names where the data comes from: online ATC data from VATSIM, and the airspace boundaries from the VATSpy Data Project (centers) and the SimAware TRACON Project (approach areas), both CC BY-SA 4.0.
Coming in a future version of FlightLog Analyzer — here’s a first look.
Keep your hands off the cockpit knobs. From the ATC View you’ll tune any controller with one click, flip the frequency to active when you’re handed off, and read the ATIS weather in plain English, all without touching Flight Simulator.
• COM1 / COM2 — next to every frequency in a VATSIM popup, ATIS included. One click puts it in that radio’s standby, never straight into active, so a misclick can’t cut you off from the controller you’re talking to.
• SWAP — under each button: flips that radio’s standby and active, like the radio’s own flip-flop key. For a few seconds a green bubble over the button shows what the radio now has active, with the controller’s callsign, read straight back from the sim.
• Decode the weather — at the top of every ATIS: its wind, visibility, weather, clouds, temperature and altimeter in plain English, above the ATIS text. An ATIS that gives its weather in words gets the airport’s real-world METAR decoded instead, which VATSIM’s weather follows.

Left: an airport’s popup under its full name, each position with its COM1 / COM2 and SWAP buttons. Right: an ATIS with its weather decoded
The buttons are in the ATC View on your PC while FlightLog Analyzer is connected to the sim; the Tablet View doesn’t show them. Some airliner add-ons run their own radios and may ignore them: the button turns red when the sim doesn’t take the frequency, so you know to tune it in the cockpit.
The buttons tune Flight Simulator’s radio; they don’t connect you to VATSIM. To hear the controllers and talk to them, fly connected to VATSIM through a pilot client such as vPilot, and turn off the sim’s own ATC. Without it, Flight Simulator’s AI controller answers on that frequency instead, because the sim uses the same real-world frequencies.
The aircraft icon marks your current position and heading. Trailing behind it is the path you've flown so far, color-coded according to the mode selected in the lower-left dropdown.
Changing the color mode mid-flight repaints the entire track immediately. The track persists through pauses and after the flight ends. Starting a new flight (or exiting the sim) clears it.
Choose from the following telemetry-based coloring modes:
• AGL Altitude — relative height above ground level. Red marks the lowest points; blue marks the highest.
• MSL Altitude — relative height above mean sea level. Same red-to-blue scale as AGL.
• True Airspeed — relative TAS. Red marks slow segments (near stall); blue marks the highest speeds.
• Ground Speed — relative ground speed. Useful for spotting headwind/tailwind effects when compared against TAS.
• G-Load — bright red for highest positive G; bright yellow for most negative; black for normal 1 G flight.
• Vertical Speed — bright green for highest climb rate; bright red for steepest descent; black for level flight.
• Sim Rate — segments flown under accelerated sim rates are colored distinctly, making it easy to spot where you fast-forwarded.
• Fuel Burn – how fast fuel is being used, per hour: red for the heaviest burn of the flight, blue for the lightest. It is worked out over about three minutes of flying, so it is gray at the very start, after a gap in the recording, where fuel was added, and on flights recorded before FlightLog Analyzer 3.4.5.0. Hover the track to read the rate: gallons per hour, or pounds per hour for jets, turboprops and turbine helicopters.
• Fuel Remaining — how much fuel is on board: blue for the most this flight had, red for the least, so you can see where it ran low. It is gray on flights recorded before FlightLog Analyzer 3.4.5.0. Hover the track to read it: gallons, or pounds for jets, turboprops and turbine helicopters. When the fuel was loaded on the ground after the flight began (the sim’s default load, then yours a moment later), the scale starts from the load you took off with, and the readings before it are gray. The same goes for Fuel Remaining as the profile’s second line.
The HUD floats over the map and displays live flight conditions in real time — altitude, airspeed, heading, G-load, vertical speed, and more. It also shows the WIND – the true direction it blows from and its speed, or Calm – and the FUEL on board, in gallons – or in pounds for jets, turboprops and turbine helicopters, as their pilots count it. If you'd rather not see it, close it with the arrow at its upper-left corner. It can be reopened at any time from the View menu.
AGL is your height above the ground the way a radio altimeter reads it: about 0 ft with the wheels on the runway, counting down to 0 at touchdown. The same goes for the altitude profile and Color Track By AGL. Flights recorded before FlightLog Analyzer 3.5.1.0 show the height of the aircraft’s center above the ground instead, which reads a few feet even when parked – about 4 ft for a Cessna 172 and 10 ft for an airliner.
IND is your indicated altitude, what the altimeter shows, which is what ATC and the charts go by; MSL is your true altitude, so in non-standard weather the two can differ by a few hundred feet. BARO is your altimeter setting, in inHg and hPa. It turns amber when it looks wrong: below 18,000 ft, when it's more than 0.03 inHg (about 30 ft) off the pressure where you are; at or above 18,000 ft, when it isn't on standard, 29.92. Hover over an amber BARO to see what it should be, or click it and FlightLog Analyzer sets the altimeter in the sim for you, just like the sim's B key. A few aircraft with their own avionics keep their own setting; if BARO stays amber, set it in the cockpit. IND and BARO show -- on flights recorded before FlightLog Analyzer 3.4.9.0.

Sitting on the runway, BARO in amber: the altimeter is set to 29.74 where the pressure is 30.16, so IND reads 385 ft below the field. Hover to see what it should be; click to set it.

One click later: the altimeter in the sim is set to 30.16, and IND reads the field elevation, the same as MSL.
Below the HUD, a second slide-out panel controls which categories of navigation waypoints are plotted on the map: VOR (V), NDB (N), Intersection (I), Traffic Pattern (P), Airport (A), and User (U) waypoints. Click its tab to expand or collapse the panel, then check or uncheck individual types — or use the All / None / Invert buttons for quick bulk changes. The filter is remembered separately for the live ATC View and for Mission Debrief replays, so hiding intersections while replaying an IFR flight, for example, doesn’t also hide them the next time you fly live.

The Waypoint Filter panel, expanded
Below the map is the altitude profile — a cross-sectional view of your flight that updates as you fly. Use the dropdown in the lower-right of the profile to choose what it plots: MSL, AGL, true airspeed, ground speed, vertical speed, angle of attack, G-load, sim rate, fuel remaining or fuel burn. Where a value wasn’t recorded — fuel on flights from before FlightLog Analyzer 3.4.5.0, say — the line has a gap there instead of dropping to zero. Max and min values for the selected parameter are shown on the left edge.
One more choice, Profile: Route (Vertical), turns the strip into a side view of your entire flight plan, with the terrain along the way — see The Route (Vertical) Profile below. The PROFILE tab in the strip’s top-left corner folds the strip down to a single line when you want more map (see Collapsing the Profile Strip).
Both draw your altitude, but they answer different questions.
• MSL, AGL and the other flown profiles – the flight as it happened, from where the recording began to where the aircraft is now, left to right in the order you flew it. MSL is your height above sea level; AGL is your height above the ground directly under you. The line ends at the aircraft and grows as you fly, so nothing ahead of you is shown.
• Route (Vertical) – your flight plan seen from the side. Left to right is distance along the planned route, from departure to destination, so it shows what is still ahead: the planned climb, cruise and descent with the TOC and TOD, the terrain under the whole route and each leg’s safe altitude. Your own altitude is drawn over it as you go.
Use MSL or AGL to look at what you did – with a second line, against any other value. Use Route (Vertical) to look ahead: where the descent should start, and whether the plan clears the terrain.
There is no second line in Route (Vertical). Its scale runs by distance along the plan, out to the destination, while the second line’s values (speed, vertical speed, G and the rest) exist only for the stretch you have flown, in the order you flew it – and anywhere you flew off the planned route has no place on a distance-along-the-route scale. So the 2nd Line picker is hidden while Route (Vertical) is chosen.
To see two things at once — say altitude and vertical speed, or airspeed and angle of attack — pick one from the 2nd Line dropdown just left of the profile’s own dropdown. It draws in amber over the main line, on its own scale, with its own max and min after the main line’s. Both share the same time axis, so hovering (or playback in Mission Debrief) marks the moment on both and shows both values, and the event ticks line up with both. Choose 2nd Line: Off to turn it off; FlightLog Analyzer remembers your choice. It isn’t available in Profile: Route (Vertical), whose strip runs by distance along the route rather than through the flight.

MSL altitude (green) with vertical speed as a second line (amber), each on its own scale.
Hovering the mouse over the profile marks that point with a green dot and displays the corresponding value at that moment in the flight. The same point is highlighted on the map above with a matching green dot, so you can see precisely where in the route a peak G-load or maximum altitude occurred.
While the mouse is in the profile section, the HUD switches to "history mode" — its text turns amber and it shows the telemetry values from that point in the flight rather than the live values. Move the mouse away and the HUD returns to real-time display.
Choose Profile: Route (Vertical) — the first entry in the profile strip’s dropdown — to see your whole flight plan from the side while you fly it, with the terrain along the entire route. It answers the questions a pilot keeps asking on the way: where will I level off, is my altitude safe over the terrain ahead, where do I need to start down, am I high or low on the way in, and have I wandered off my route? If TOC, TOD, the 3° path and safe altitude are new to you, read the chapter Vertical Profiles Explained first.

The Route (Vertical) profile in cruise at 12,500 ft from Phoenix to Las Vegas: the climb and level-off (TOC), the terrain along the whole route and each leg’s safe altitude (red), and the planned descent (TOD 32.4 nm before KLAS).
1. Load a flight plan in MSFS — Build or load a plan with a cruise altitude: in the World Map, from SimBrief, or by loading a .PLN you exported from FlightLog Analyzer’s Flight Planner (Appendix A walks through every screen).
2. Start the flight with FlightLog Analyzer running — The ATC View opens as usual and reads the plan’s destination, waypoints, departure airport and cruise altitude, then fetches the terrain for the route in the background.
3. Pick the mode — In the dropdown at the top-right of the profile strip, choose Profile: Route (Vertical). FlightLog Analyzer remembers the choice for your next flights and for Mission Debrief windows.
• Dashed amber line — the plan: the climb from the departure’s field elevation, the cruise, and the 3° descent to the destination’s field elevation.
• TOC marker — the amber dot where the climb ends, labeled with its distance from the departure (“TOC 46.0 nm”). It shows (est) until you actually reach cruise.
• TOD marker — the amber dot where the descent should begin, labeled with its distance before the destination (“TOD 32.4 nm”).
• Green line — the altitude you have actually flown, plotted against distance along the route, with a dot at your current position.
• Light brown fill / dashed outline — the terrain along the planned route: a fill ahead of you, a dashed outline over the part you have already flown.
• Solid brown — the terrain you have actually flown over, as reported by the simulator.
• Red line — each leg’s safe altitude, with the highest labeled (“SAFE 12,400”).
• Red banner — “⚠ CRUISE BELOW SAFE ALTITUDE”, if the plan’s cruise altitude is below the route’s safe altitude.
• Ticks and names — every waypoint in the plan at its distance along the route. When names would overlap, some are skipped; the destination’s name is always shown.
• Legend and SCALE — just under the summary line. SCALE gives the altitude at the bottom and the top of the strip.
The line of white text across the top of the strip is the profile’s dashboard. Which items appear depends on where you are in the flight. The examples below are taken from the pictures in this section:
|
What you see |
What it means |
|
ROUTE 977.5 nm |
Total length of the planned route, from the departure through every waypoint to the destination. |
|
CRUISE 12,500 ft |
The plan’s cruise altitude. It reads PEAK instead when the route is too short to reach cruise (see When the Route Is Too Short to Reach Cruise). |
|
TO DEST 539.5 nm |
Distance left to the destination, measured along the route from the point on the route nearest to you. |
|
TOD IN 507.0 nm (~203 min) |
Before the descent: the distance — and, at your current ground speed, the time — until you should start down. |
|
3° PATH 5,836 ft (942 ft high) |
After TOD: the altitude a 3° path calls for at your position, and how far above (“high”) or below (“low”) it you are. Within 100 ft it says “on path”. |
|
OFF ROUTE 3.6 nm |
Appears whenever you are more than 1 nm to the side of the planned route. |
|
SAFE ALT 12,400 ft |
The highest leg safe altitude on the whole route (see Safe Altitude). Appears once the terrain has loaded. |

Past TOD on the way into KLAS: a 3° path calls for 5,836 ft at this point, and the aircraft is 942 ft above it.
Here is how the strip behaves over a whole flight — Phoenix (KPHX) to Las Vegas (KLAS) at 12,500 ft, the route in the pictures above:
Before departure — The amber plan is already drawn, and within a few seconds the terrain along the route and the red safe altitude steps appear. SAFE ALT 12,400 ft is below the 12,500 ft cruise, so there is no warning. TOC is an estimate — 300 ft per nm up from KPHX’s 1,135 ft — marked (est).
Climbing — After a minute or so of climb, the TOC estimate switches to your measured climb gradient. A steeper climb than 300 ft per nm moves it left (sooner); a shallower one moves it right.
Leveling off — When you reach cruise (within 100 ft), the TOC marker jumps to exactly where you leveled off and loses its (est) label.
Cruise — TOD IN counts down. At 150 kt, “TOD IN 30.0 nm (~12 min)” means twelve minutes until you should start down — a good moment to get the weather and the arrival briefed. Glance at the light-brown terrain ahead and the red safe-altitude line to see what is coming.
Descending — Past the TOD point the countdown is replaced by 3° PATH. If it says “900 ft high”, increase your descent rate; if it says “low”, shallow it out — and keep the red safe-altitude line of the leg you are on in mind. The five-times-ground-speed rule from the Tip in the vertical profiles chapter keeps you close to “on path”.
Arrival — TO DEST counts down to 0.0 nm as you reach the destination.
If you leave the planned route — weather, ATC vectors, a little sightseeing — the summary adds OFF ROUTE and the distance as soon as you are more than 1 nm to the side, and drops it again once you are back within 1 nm.

Mid-flight, 3.6 nm north of the planned route: “OFF ROUTE 3.6 nm”.
The profile keeps working while you are off route: your position is always measured against the nearest leg of the route, so the distance along the route, TO DEST and TOD IN all stay sensible. Keep in mind that the route terrain and safe altitudes describe the planned route’s corridor (4 nm either side) — once you are well off route, they no longer describe the ground beneath you. The solid brown terrain flown over always does.
If the flight plan’s cruise altitude is lower than the route’s safe altitude, a red banner appears across the top of the chart (or, with the strip folded, in red at the end of the summary line). Here is the same Phoenix–Las Vegas route flown with a plan cruise altitude of 6,001 ft — the green line shows the aircraft having to climb over the terrain on its own:

A 6,001 ft plan over terrain that reaches 11,339 ft: “⚠ CRUISE BELOW SAFE ALTITUDE (12,400 ft)”.
The fix is in the plan, not the profile: pick a cruise altitude at or above SAFE ALT, or choose a route around the high ground — the Flight Planner shows the same warning before you fly.
Move the mouse over the strip and a cursor line follows it with a readout. What the readout shows depends on whether you have flown that part of the route yet:
• Over the part you have flown — the distance along the route, the altitude you were at, the ground height there, the planned altitude (when there is a plan), how far off route you were (if half a mile or more), and that leg’s safe altitude. The same point is marked on the map with a green dot, and the HUD switches to history mode, exactly as in the other profile modes. For example, from a real flight:
15.1 nm flown 6,530 ft / gnd 5,046 ft off route 6.0 nm
• Ahead of the aircraft — the distance along the route, the planned altitude, and the ground and safe altitude there from the route terrain, so you can look ahead. For example, 600 nm along the Phoenix–Las Vegas route:
600.0 nm plan 12,500 ft gnd 6,230 ft safe 9,300 ft
When the profile can’t draw a route, it says why in the middle of the strip. While you are flying, some of these clear up by themselves:
|
Message |
What it means |
|
Route profile needs a flight plan -- load one in MSFS (or the Flight Planner) before the flight |
No flight plan was loaded, and the profile needs a route to draw. Load a plan before the flight, or choose another profile mode. |
|
Route profile: waiting for the first aircraft position (the flight plan has no departure airport FLA recognizes) |
The plan has a destination but no departure airport FlightLog Analyzer knows, so the route will start from wherever the aircraft is first seen. This clears as soon as telemetry starts arriving. |
|
Route profile: this flight plan starts and ends at the same place, so there is no route to draw -- try Profile: MSL Alt |
A local or traffic-pattern flight planned from an airport straight back to itself has no route to profile. Profile: MSL Alt shows your altitude over time instead. |
|
(no planned cruise altitude available) |
Shown in the summary line when the plan carries no cruise altitude. There is no planned line, but everything else still works. |
|
(plan cruise altitude 500 ft is below the airports) |
The plan’s cruise altitude is not usable (see the Note in Where the Numbers Come From). Again, everything except the planned line still works. |
No terrain and no SAFE ALT? The terrain couldn’t be downloaded (for example, no internet connection) and wasn’t already cached. Everything else on the profile works without it.
The control panel in the lower-left corner provides quick access to aviation chart overlays. The Map Overlay dropdown selects which chart to display:
• IFR Low Enroute
• IFR High Enroute
• VFR Sectional
• and others (see the dropdown for the current list)
|
Note: The VFR Sectional, TAC (Terminal Area), IFR Low Enroute, and IFR High Enroute overlays are USA-only. The FAA publishes its aeronautical charts in the public domain, which is what lets FlightLog Analyzer offer them freely. Most other civil aviation authorities don't release their charts that way, so for flights outside the USA the Worldwide Airspace overlay is the best (and effectively only) option. |
The Aviation Layer slider above the dropdown adjusts the overlay opacity, letting you balance chart readability against the underlying street/satellite map. When you switch between overlays, the layers cross-fade for a smoother transition.

Map Overlay options and Aviation Layer slider
When a flight plan with one or more waypoints is loaded, FlightLog Analyzer draws destination lines on the map to help you see the remaining route at a glance:
• Static dashed line — connects each waypoint in sequence all the way to your final destination, giving you a persistent picture of the planned route.
• Dynamic active-leg line — runs from your aircraft's current position to the active waypoint, updating in real time as you fly.
Both lines follow the real great-circle path between points rather than a flat straight line — on a long leg (a transatlantic flight, for example) the line visibly bows toward the pole on the map instead of cutting a diagonal across it, the same rendering the Flight Planner uses for its own route line.
Each leg displays a bearing/distance label at its midpoint — for example,
183° / 32.1nm / 4min — so you can read the heading and distance for each successive fix without cluttering the waypoint markers themselves. The label on the active leg includes a third value: the estimated time to the next waypoint (or to the destination when no intermediate waypoints remain).
The time-to-waypoint value isn’t just “distance ÷ ground speed.” It uses only the component of your ground speed that lies along the bearing to the next point (and is then scaled by the current sim rate). In other words, it answers: at your present heading and speed, how fast are you actually closing on the waypoint? If your heading is straight at the target, the full ground speed counts and the time matches what you’d expect. As your heading drifts away from the target bearing, only the projected component counts, so the time gets longer. Once your heading is more than 90° away from the bearing to the waypoint, the projected component is zero or negative — you are no longer making any progress toward it — and the label shows ∞ to indicate that, at your current heading, you will never reach the waypoint.
Toggle destination lines on or off with F6 (or the Dest Lines: ON/OFF button in the control panel).
Change the contrast of the destination lines with the slider, to adjust for best visibility on the Map Overlay that you’re using

Contrast of Destination Lines
|
Note: On the first flight after starting MSFS, the en-route waypoints typically can't be plotted on the map. The destination airport still resolves correctly, so you'll see the active-leg line to the destination, but intermediate waypoint markers and per-leg labels will be absent. This is a known MSFS bug — not an issue in FlightLog Analyzer — and subsequent flights in the same MSFS session work normally. It is also a bug within MSFS that when importing a Flight Plan File (.PLN), the waypoints of the flight are likely to not resolve correctly. This is apparent within MSFS, as you will see the ‘World Map’ will not show the waypoints correctly after closing the Flight Plan Builder screen. |

Destination lines with per-leg bearing, distance, and ETA labels
The active waypoint advances automatically as you fly: once your aircraft comes within roughly 1.5 nautical miles of the current fix, FlightLog Analyzer moves the active-leg line forward to the next waypoint in the route.
When you need to jump ahead or step back manually — for example, when ATC vectors you around a fix — use the left and right arrow buttons in the waypoint navigator at the bottom-center of the map. The navigator also shows your current position in the sequence (for example,
1/4 Catalina), so you always know which fix is active and how many remain.

Destination lines and the waypoint navigator
FlightLog Analyzer uses a three-tier fallback chain to determine your destination airport when loading a flight:
1. First, it checks the ATC aircraft record in the .flt file.
2. If that's unavailable, it looks for an explicit Arrival ICAO field.
3. As a last resort, it parses the associated customflight.pln XML file — including flights where the world position is stored in degrees/minutes/seconds (DMS) format.
The result is that the destination airport label and its associated route lines resolve correctly for virtually any flight plan type, whether created by the sim's built-in planner or a third-party tool.
Each aviation chart overlay (VFR Sectional, TAC, IFR Low/High, Worldwide Airspace) only renders useful detail within its own zoom range — too far out and the chart is blank or unreadable. Rather than hunting for the right zoom level by trial and error, press F3 (or the Snap to Overlay Zoom button in the Map Controls panel) to jump straight to that range: if you’re zoomed out too far, it zooms in to where the chart starts showing detail; if you’re zoomed in past where the chart is useful, it zooms back out to the chart’s maximum. The button dims itself whenever the current zoom is already within the active chart’s range, since pressing F3 wouldn’t change anything in that case.

The Map Controls slide-out panel, showing the new Snap to Overlay Zoom (F3) button
Resizes the map to include the entire flight path. It zooms once per press — it does not continuously re-fit.
Toggles automatic centering. When on, the map continuously re-centers on the aircraft so your plane stays in the middle of the view.
Toggles the destination lines (described above) on and off.
Right-click anywhere on the map and choose Clear flight track… to erase the painted flight path (it asks first). Your recorded telemetry is not affected. You rarely need it: the track starts over by itself with each new flight, and when the sim stops. It is for a track that went bad mid-flight, for example after slewing or teleporting in the sim. A shared flight, and the Tablet View, are cleared along with it.
When something goes wrong in flight, the first question is where to land. Press F7 in the ATC View — or click 📍 (F7) Nearest Airports in MAP CONTROLS — for the ten closest airports with a runway you could land on, nearest first. Press F7 again, or click ✕, to close it.
• Dist — the straight-line distance from your aircraft, in nautical miles.
• Brg — the magnetic course to fly direct to the airport. Where no magnetic variation is known (far out over the ocean, for example) the course is true instead, and marked T.
• Time — how long it would take at your current ground speed. It stays blank below 30 knots, on the ground.
• Longest runway — the length and surface of the airport’s longest usable runway; 💡 means it is lighted. Hover over a row for the runway’s name and width and the field elevation.
• Best wind — the runway best into the wind at that airport, with its headwind (or tailwind) and crosswind, from the airport’s real-world weather report (METAR); hover over it for the full report. It stays blank for a few seconds until the report arrives, and at airports that don’t issue one, and it is shown in orange for a tailwind or a crosswind of 15 kt or more. If the sim isn’t flying with live weather, its wind can be different.
• Keeping up — the distance, course and time follow your aircraft as you fly; which airports are on the list is checked again every 10 seconds.
• Runway length — pick the shortest runway you would accept, from Any runway length up to 8,000 ft or longer.
• Paved only — tick it to leave out turf, gravel and dirt strips.
• Never listed — heliports, seaplane bases, balloonports and closed airports, as well as water runways and helipads. An airport with no runway on file is left out too, since there is no way to check its runway.
Both choices are remembered for next time.
Click an airport in the list to draw a dashed line to it from your aircraft, labeled with its code and distance; the map zooms out to show both. The line follows your aircraft as you fly. Click the same airport again to take the line away.

The Nearest Airports list (F7) with Glenwood picked: the line runs from the aircraft to the airport, and the distance beside it counts down as you fly.
• Live flights only — it isn’t in Mission Debrief, and it isn’t shown in the Tablet View.
• Where the data comes from — the same free airport and runway database the Flight Planner uses. An add-on airport, or a field the simulator has changed, may differ from it.
• 300 nm — the search reaches 300 nautical miles; past that (mid-ocean) the list simply comes up short.
How far is that lake, and what course would take you there? Press M — or click 📏 (M) Measure in MAP CONTROLS — and click points on the map. It works in the ATC View and in Mission Debrief.
• Start — press M or click Measure. The pointer becomes a crosshair, and a readout appears above the waypoint buttons.
• Click the first point — or, flying live, click From aircraft in the readout to measure from where your aircraft is.
• Click the next point — a line follows the pointer, labeled with the distance and course to it. Keep clicking to measure several legs in a row: each leg is labeled, and the readout adds them up.
• Finish — press Esc, double-click the last point, click Done, or press M again. The legs you have placed stay on the map until you click Clear.
• Made a mistake? — Backspace takes back the last point while you are measuring.
• Distance — in nautical miles along the great circle, for each leg and in total.
• Course — the magnetic course from each point to the next, using the magnetic variation near the first point. Where no variation is known (far out over the ocean, or in the Tablet View) the course is true instead, marked T.
• Time — flying live, the readout also shows how long the whole distance would take at your current ground speed.

A five-leg measurement around Sedona: each placed leg labeled with its distance and magnetic course, the dashed line following the pointer to the next point with the running total, and the readout below.
Will you land before dark? Press Ctrl+F11 — or tick (Ctrl+F11) Day / Night in MAP CONTROLS — and the night side of the earth is shaded on the map, in three steps that get darker: the sun below the horizon, below 6° (civil twilight) and below 12° (nautical twilight). It is on to begin with; press Ctrl+F11 again to turn it off, and FlightLog Analyzer remembers your choice. The same setting is also in the View menu, as Day / Night Shading on Maps, right under Dark Mode Toggle.
• What the bands mean — the first band starts at sunset (and ends at sunrise). The second, from the end of civil twilight, is night as the FAA defines it for logging night time and for position lights (14 CFR 1.1). In the third the horizon can no longer be seen: it’s effectively dark. Night currency for carrying passengers follows a different rule, from 1 hour after sunset to 1 hour before sunrise, so a landing in the second band doesn’t necessarily count toward it (see Pilot Currency).
• By the sim’s clock — the shading follows the time of day in the sim, not on your PC, so a flight you set at dusk shows dusk even at noon at home. It moves as the flight goes on.
• Mission Debrief — the shading shows the moment you are hovering or playing back, so you can watch the sun set during a replay. Flights recorded before FlightLog Analyzer 3.4.6.0 didn’t record the sim’s clock as they went, so for them it goes by the flight’s Sim Date Time from the logbook.
• Everywhere else — in the main window and the other windows, Ctrl+F11 still turns the grids’ horizontal lines on and off; only in the ATC View and Mission Debrief is it the shading. In the Tablet View, use the checkbox.

Day / night shading at dawn over the Mediterranean: the darker the band, the lower the sun.
See who else is out there. The ATC View shows the other aircraft your sim has around you, within about 100 nm, moving on the map as they fly: Flight Simulator’s own AI and live traffic, other pilots in multiplayer, and VATSIM or IVAO pilots that your vPilot, xPilot or Altitude client brings into the sim. Tick or untick Traffic in MAP CONTROLS to turn it on or off; it is on to begin with, and FlightLog Analyzer remembers your choice.
• Cyan plane — an aircraft in the air, pointing the way it’s heading.
• Gray plane — an aircraft taxiing on the ground. Parked aircraft aren’t shown: a big airport has dozens of them.
• Label — its callsign and altitude: in feet below 18,000 ft, as a flight level above (FL247), and “ground” when taxiing, with an arrow when it is climbing (↑) or descending (↓) at 300 fpm or more. Labels appear once you zoom in (zoom level 8 or closer), so a zoomed-out map isn’t buried in text. Labels for aircraft on the ground wait until you’re zoomed in close to the airport (zoom level 14 or closer), since a busy airport’s taxiways would otherwise pile them on top of each other.
• Click a plane — for its callsign and aircraft type, its altitude above sea level (MSL) and above the ground (AGL), its ground speed and vertical speed, and its heading. The popup keeps updating while it’s open.

Traffic around Chicago O’Hare: each aircraft in the air with its callsign and altitude; the ones on the ground are unlabeled until you zoom in close.
• Smooth movement — FlightLog Analyzer gets each aircraft’s position every 2 seconds and moves it along its heading in between, so the traffic glides rather than jumps.
• Only what your sim has loaded — the traffic comes from your own Flight Simulator, not from an online network, so it shows the aircraft the sim has around you right now, and only while FlightLog Analyzer is connected to it.
• Mission Debrief — shows no traffic: other aircraft aren’t recorded with your flight.
• Tablet View — shows the traffic too, with its own Traffic checkbox.
On a long flight you may not be watching the screen when it is time to start down. FlightLog Analyzer can chime and show a banner a few minutes before the planned top of descent (TOD), and again when you reach it — in the ATC View, and on a tablet showing the Tablet View, so you can leave the flight on autopilot and still be back in time.
• Choose the warning time — in MAP CONTROLS, Top of Descent Alert: Off, or 2, 5, 10 or 20 minutes before. Each screen remembers its own choice, so the PC and the tablet can differ.
• Pause the sim at TOD (optional) — tick Pause the sim at TOD under the warning time, and the ATC View also pauses Microsoft Flight Simulator when you reach the top of descent, so the flight waits for you even if you missed the chime. The banner then shows The sim is paused, with a Resume button (see the warning below). This needs FlightLog Analyzer connected to the sim, and it is only in the ATC View on the PC: the Tablet View shows the alert but cannot pause the sim.
IMPORTANT — once FlightLog Analyzer has paused the sim, you MUST resume it from the ATC View. Go to the PC and click ▶ Resume in the TOP OF DESCENT banner at the top of the ATC View. Do not try to unpause from inside Microsoft Flight Simulator: the sim’s own Esc menu does not undo this pause, and the flight stays frozen. The Tablet View cannot resume it either. So that the Resume button is always there, the banner cannot be dismissed while the sim is paused. (Closing the ATC View, or FlightLog Analyzer itself, while the sim is paused resumes the sim for you.)
• Fly with a flight plan that has a cruise altitude — the alert uses the same top of descent as the route profile: the 3° descent path back up from the destination to the planned cruise altitude. With no flight plan, or a plan whose cruise altitude is missing or below the airports, there is no TOD to warn about, and the alert stays quiet.
• Before the TOD — one chime and an amber banner, for example TOP OF DESCENT IN 5 MIN, with the distance to go. The banner counts down until you get there.
• At the TOD — two chimes and an orange banner: TOP OF DESCENT, start down now. If you have already started down early, it stays quiet.
• The time — is measured along the planned route, at your current ground speed.
• Dismiss — click or tap the banner. Each alert sounds once per flight plan.
• One tap for sound — tablets and phones only let a web page play sound after you have touched it. While the alert is on, the Tablet View shows Tap to enable the top of descent alert sound. Tap it, and you hear the chime once, so you know how loud it will be. Any tap on the page does the same.
• Keep the screen on — a tablet stops running the page when its screen locks, so it cannot chime. Plug it in and set it not to lock during the flight: on an iPad, Settings > Display & Brightness > Auto-Lock > Never; on Android, Settings > Display > Screen timeout.
• Volume — turn the tablet’s volume up before you walk away.

Five minutes to the top of descent: the banner counts down, and the route profile shows where the descent starts.
Fly with the ATC View on an iPad or an Android tablet beside you: the same live map, HUD and profile, in the device’s own web browser. There is no app to install and no account to create — FlightLog Analyzer serves the view itself, on your home network.
• Open the switch — in the ATC View, open MAP CONTROLS (the MAP tab at the lower left) and click 📱 Tablet View.
• Turn it on — click Turn on. The panel shows an address such as http://192.168.1.20:8456/ and a QR code. Click the address to open the Tablet View in this PC’s own web browser, to check it or to show it on a second screen.
• Open it on the tablet — on a tablet connected to the same Wi-Fi as the PC, scan the QR code with the camera, or type the address into the web browser. Bookmark it, or add it to the home screen, for next time.
The first time, Windows may ask whether FlightLog Analyzer may communicate on networks: allow it on private networks (your home network), or tablets won’t be able to reach it. FlightLog Analyzer remembers that the view is on and starts it again whenever the ATC View opens. The panel shows how many screens are watching; Turn off stops it.

The Tablet View button in MAP CONTROLS (with the number of screens watching), and the panel it opens: the address to open and a QR code to scan.
• Live — the badge at the top left says ● Live from FlightLog Analyzer. If the connection drops — the PC went to sleep, or the tablet left the Wi-Fi — it says Reconnecting, and catches up by itself as soon as it can.
• The flight so far — open it mid-flight and you still get the whole track flown so far, not just what happens from then on.
• Your own view — map overlay, track coloring, profile, auto-center and which panels are open are chosen on the tablet and remembered on that device. They don’t change the ATC View on the PC, and nothing on the tablet can change anything in FlightLog Analyzer.
• Touch — drag a finger along the profile to look back at any moment of the flight, just as hovering the mouse does; lift it to go back to live.

The ATC View on an iPad: the live flight around Chicago O’Hare, with its own choice of track coloring and a second line on the profile.
• The ATC View must be running — it can be minimized, but the tablet shows what the ATC View shows. Like the ATC View, it needs the PRO version once the trial period ends.
• Home network only — only devices on your own network can open it; nobody on the internet can. Guest Wi-Fi networks often keep devices apart, so a tablet on guest Wi-Fi may not reach the PC.
• If the address doesn’t open — check that the tablet is on the same Wi-Fi as the PC. Many homes have two: the modem’s own Wi-Fi and a mesh or extender system with a different name, and a device on one can’t reach a PC on the other (on the tablet, the start of its IP address, under Settings → Wi-Fi, should match the start of the address shown in the panel). Also try the second address if the panel lists one, and make sure Windows was allowed to let FlightLog Analyzer on the network (Windows Security → Firewall & network protection → Allow an app through firewall). If another program already uses port 8456, the panel says so.
• The tablet still needs the internet — for the map itself and the aviation charts, which it downloads directly, just as the ATC View does.
• Live flights only — Mission Debrief isn’t shown on the tablet.
Flight Alerts show on the Tablet View too, with their sounds once you’ve tapped the page: see Flight Alerts.
Your flight, shared live with friends and family anywhere in the world, as many as you like, all at once. One click in the ATC View gives you a link, and whoever opens it watches your flight as you fly it: the same moving map, HUD and altitude profile, in any web browser on any phone, tablet or computer. There’s no app to install and no account to create, for you or for them, and nothing to set up on your network.
• Open the panel — in the ATC View, open MAP CONTROLS (the MAP tab at the lower left) and click Share Live Flight.
• Start — type your name or callsign if you like (it’s shown on your friends’ page and in its browser tab), and click Start sharing.
• Send the link — Copy link puts it on the clipboard for a text message, Discord or a forum post; Email starts a new email with the link in it; Open shows you the page your friends see. Send it to as many people as you like: they all watch the same flight at once.
Sharing needs a PRO license. Watching needs nothing at all: anyone with the link can watch.

The Share Live Flight button in MAP CONTROLS, with the number of people watching.

Sharing: the link to send with Copy link, Email and Open, how often updates go out and how many people are watching, and Stop sharing.
• The live flight — your track, the HUD and the profile, a few seconds behind you. The badge at the top says LIVE, your name, and how often the page updates.
• The flight so far — open the link partway through and the whole flight appears, from the departure on.
• Their own view — map overlay, track coloring, profile and zoom are chosen on their screen; nothing they do changes your ATC View or your flight. On a computer, F4 (Auto-Center), F5 (Zoom to Flight) and F6 (Dest Lines) work on the page just as they do in the ATC View.
• When it’s over — when you stop sharing or close FlightLog Analyzer, the badge says Flight ended and the track stays on the page. It stays when you land and the sim stops, too: the finished flight is still there for anyone who opens the link, until your next flight begins.
• Earlier flights — once you have flown more than once on the same link, a Flights button appears under the badge. It lists your last five flights, newest first, each with its route (KORD → KJFK) and the time it began. Tap one to watch it from the departure on; Back to the current flight returns. Friends who are watching your current flight move on to your next flight by themselves.

A friend following the flight live in a web browser, over Lake Powell.
• What’s shared — your aircraft’s position and flight data (what the HUD shows), your flight plan’s route and destination, and the traffic around you. Nothing from your logbook, and nothing about you but the name you type.
• Your link is yours for good — it is the same address every time you share, however long it is between flights, so friends can keep it for good. Each new flight is added to the same page, and the last five stay on it for your friends to look back at. When you are not sharing, the page says so and opens your flight as soon as you start.
• Busy times — when many pilots are sharing at once, the website takes updates a little less often (every 2 to 5 seconds instead of every second). Your panel and your friends’ badge show the current rate, and the flight still plays back at the pace you flew it.
• Internet hiccups — if your connection drops, FlightLog Analyzer keeps the updates and sends them as soon as it’s back; nothing is lost.
• The ATC View must be running — it can be minimized. Like the Tablet View, it shares live flights only, not Mission Debrief.
• How long the flights stay — after you stop, the page says the flight ended and keeps your flights for a day; after that it says you are not sharing right now, and shows your flight again whenever you start.
• If your link gets out — in the Share panel, click Get a new link… (it asks first). The old link stops working for everyone who has it, your earlier shared flights on it are deleted, and you get a new address to send. Sharing carries on right away if it was on.

The Share panel. Get a new link… gives up your link for a fresh one.

It asks before it does anything.
People watching are told when you’re about 10 minutes from landing, and when you’ve landed, so they don’t miss it: see For Friends Watching a Shared Flight.
Where do you really fly? The Airport Heat Map lights up every airport you’ve ever departed from or landed at, sized by how often you’ve been there. Spot your home bases at a glance, see the corners of the map you’ve never touched, and find your next destination in the gaps.
The Airport Heat Map plots every airport you’ve flown from and to on an interactive map, with dot size scaled to how many visits each airport has had. Open it from the Airport Heat Map button on the main toolbar.

VFR Sectional overlay, zoomed in on the Prescott (KPRC) area — hovering a dot shows the airport name and visit count
The From airports checkbox (green dots) and To airports checkbox (red dots) in the legend let you isolate departures or destinations independently. Hovering any dot shows the airport identifier, name, and number of visits.
The Map Overlay dropdown switches the underlying chart — VFR Sectional for the detailed aeronautical view above, or a broader Worldwide Airspace view for seeing your overall flying footprint:

The same data with the Worldwide Airspace overlay, zoomed out to show the wider western-US flying footprint
The Navigation Database window shows exactly how much airport, navaid, fix, and procedure data FlightLog Analyzer currently has loaded for flight planning and mapping — one independent count for each, rather than several numbers crammed onto one line. Open it from View → Navigation Database ... on the main menu.

Opening the Navigation Database from View → Navigation Database ... on the main menu.

The Navigation Database window, showing how many of each type of data is currently loaded.
Airports, VORs, and NDBs come from a free, continuously-updated public database and are shown with the date that data was last refreshed. Fixes, SIDs, STARs, and Approaches come from the FAA’s official 28-day update cycle instead, and are shown with that cycle’s effective and expiration dates — see the note at the start of the Flight Planner section for why this procedure data only covers U.S. airports.
|
Plan the flight you actually want to fly, in minutes. Pick a departure and a destination, and the Flight Planner builds the route: real SIDs, STARs and approaches at US airports, distance, time and fuel worked out for the real winds aloft, and a .PLN ready to load into Flight Simulator. Can’t decide where to go? Let Surprise Me pick an airport you’ve never been to. Loved a trip? Fly It Again puts it straight back on the map. Note: SIDs, STARs, and Approaches are currently available for U.S. airports only — the FAA is the only aviation authority that publishes this data free of charge. Every other country’s equivalent comes from paid commercial providers, and covering that ongoing cost would mean turning FlightLog Analyzer into a subscription instead of the one-time purchase it’s always been, so procedure data outside the U.S. isn’t available here for now. |
Flight Planner turns a few clicks on a map into a fully worked route: pick a departure and destination, or drop waypoints anywhere in between, and distance, time, and fuel update live as you go — corrected for the actual winds aloft at your cruising altitude, not a flat still-air guess. Real airport data, runway suggestions, and current METARs come along for the ride, and when the route is right, export a genuine MSFS flight plan (.PLN) that loads straight into the sim. Open it from the Flight Planner button on the main toolbar.

The Flight Planner window with a full route plotted, showing the Import/Export .PLN buttons, drag-to-reorder waypoint list, and the collapsible Map Controls panel.
|
Note: Flight Planner requires a PRO license once the trial period ends. |
1. Opening the Planner — Click the Flight Planner button on the main toolbar. The window opens with its own remembered position and size, and restores the map view (chart overlay, zoom, and center) from the last time you used it. In the lower-left corner, a collapsible Map Controls panel (click the MAP tab to show or hide it) holds the Zoom to Fit All button, the chart overlay dropdown, and its opacity slider — the same slide-out panel design the ATC View and Mission Debrief maps use. Press F3, or click the panel’s Snap to Overlay Zoom button, to jump the zoom level into whatever range the selected aviation chart actually renders detail at.
2. Building the Route — Add points either by typing an ICAO code into the Departure/Destination fields, or by clicking the map. A map click near a real airport, VOR, NDB, or named fix snaps to its identifier; if more than one is close together, a waypoint picker lets you choose which one you meant — candidates are grouped by type, sortable by distance or name, and filterable per type — or press Esc to dismiss it and drop a plain map point instead. The first point you add becomes the departure, the second becomes the destination, and every point after that extends the route forward — whatever was the destination automatically becomes an intermediate waypoint. You can remove any point from the Waypoints list, including the current departure or destination, and whatever’s left becomes the new start/end automatically. You can also drag any waypoint in the list to a new position to reorder the route — dragging the current departure or destination elsewhere promotes whichever point is now first/last automatically, the same as removing one does. Ctrl-click or Shift-click to select several waypoints at once — Delete (or Remove Waypoint) removes the whole selection together, and dragging any one of the selected items moves the whole block as a unit. Ctrl+Z undoes your last add, delete, or drag-reorder — repeatedly, up to the last 20 changes — and Ctrl+Y (or Ctrl+Shift+Z) redoes whatever you just undid. Typing a new Departure/Destination ICAO, Clear All Waypoints, or importing a flight plan (below) each start a fresh history instead of being folded into it, so undo never reaches back through one of those to something earlier. Clear All Waypoints asks you to confirm before wiping the whole route, since there’s no undo for it. Once an ICAO resolves, hovering over that Departure/Destination field shows the airport’s full name. If you don’t know an airport’s ICAO code, the magnifying-glass button next to either field opens a search by name or city instead — pick a result and it fills in the code for you. Typing an ICAO code directly also auto-completes it, as soon as what you’ve typed narrows down to a single match.
Adding points in the middle of the route — Select a waypoint in the Waypoints list and the next map click adds its point right after that waypoint instead of at the end of the route. The new point then becomes the selection, so clicking along the map lays down several points in order, right where you need them. The hint under the list says where the next click will go (“Click the map to add a waypoint after WP3”). To go back to adding at the end, press Esc — on the map or in the list — or click the empty space below the waypoints. With the destination selected, a click still extends the route as usual, and a new point never lands in the middle of a SID or STAR. Each new map point gets the next unused name (WP7, WP8 and so on), so names never repeat.

Typing a partial ICAO code auto-completes it once what you’ve typed narrows to a small set of matches — keep typing, or use the arrow keys and Enter/Tab, to pick one.

The Find Airport dialog, searching by name — here for every airport with “Ranch” somewhere in its name. Double-click a result, or highlight it and click Select, to fill in its ICAO code.

The waypoint picker shown when a map click lands within range of more than one airport, VOR, NDB, or fix — grouped by type, sortable by distance or name, and filterable per type with the checkboxes and All/None buttons.
When the click is genuinely ambiguous, the picker lists every candidate within range, closest first within its own type, grouped Airport, then VOR, then NDB, then named Fix — a busy area like a city full of hospital heliports can turn up dozens of candidates, so the Airports/VOR/NDB/Fixes checkboxes (with All/None to flip them all at once) narrow the list down to just the type you're after, and the By Distance/By Name buttons switch the sort order within each group. Double-click an entry, or select it and click Add, to use it; click Use Raw Point instead to add the exact spot you clicked as a plain waypoint and ignore every candidate; or press Esc (or click Cancel) to back out of the click entirely, adding nothing.

Hovering over a resolved Departure/Destination field shows the airport’s full name.

Drag a waypoint's grab handle to reorder the route.

Clear All Waypoints asks for confirmation before wiping the route.
Right under the Departure/Destination fields, a Rwy: box lets you pick which runway you plan to use at each airport — the dropdown lists every real runway on file for that airport (e.g. 09L, 27R), but you can also type your own if you’d rather. Once wind data is available for that airport, the box automatically fills in whichever runway is best aligned with the current forecast wind; with calm or unavailable wind, it defaults to the airport’s longest runway instead (landing or taking off into the wind shortens your ground roll and keeps crosswind to a minimum, which is why it's normally the more comfortable, safer choice), and either way the field stays fully editable — picking your own value stops the automatic suggestion from overwriting it until you change airports again.

The Rwy: dropdown lists every real runway on file for the airport.

Once wind data is available, the box fills in the best-aligned runway.
3. Watching It Take Shape — As you add points, the map draws the route live — a dashed line connecting each leg with its bearing and distance labeled, and green/red markers for the departure and destination. Press F5, or click the Zoom to Fit All button above the map overlay selector, to zoom the map to fit the whole route. The Distance/Time/Fuel line at the top updates continuously based on your cruise speed and fuel burn rate, which are remembered between sessions — a toggle next to the fuel burn field switches between gallons/hour and pounds/hour for turbine aircraft. A separate VFR/IFR toggle near the same fields sets a label written into the exported .PLN's flight-plan type — a plain declaration of your intent, not something FlightLog Analyzer checks the route against, since no airway or procedure database exists here to validate it with.

The Zoom to Fit All button, above the map overlay selector.
The Distance/Time/Fuel line can also account for actual forecast wind rather than assuming still air, using NOAA’s public winds-aloft forecast for the continental United States. Legs that pass through US airspace get their estimated time (and therefore fuel) adjusted for headwind or tailwind at your chosen cruising altitude; legs outside that coverage simply fall back to the still-air estimate. A Wind: ON/OFF button next to the estimate lets you compare the two directly — hovering over the Distance/Time/Fuel line shows what the estimate would be with the toggle in the other position. Hovering over any leg’s course/distance label on the map itself shows the specific forecast wind used for that leg. Hovering over a waypoint marker itself — departure, destination, or any point in between — shows the forecast wind right at that location, even before you’ve added a second point to form a leg.

The Wind: ON/OFF toggle, and the comparison tooltip on the estimate line.

Hovering a leg's course/distance label shows the forecast wind used for that leg.

Hovering over a waypoint shows the forecast wind at that point.
Below the cruise speed and fuel burn fields, the planner also shows the current METAR for your departure and destination airports once each one resolves — the same weather a pilot would check before flying this route. The text color reflects the airport’s current flight category, the same convention used on aviation weather charts: green for VFR, blue for MVFR (marginal), orange for IFR, and magenta for LIFR (low IFR) — in practice, how much you'd actually be able to see: VFR means clear enough to navigate and spot other traffic just by looking outside, while the categories toward IFR mean low enough cloud or visibility that flying by instruments (and the certification real pilots need for it) takes over, since you couldn't reliably see the ground, terrain, or other aircraft. Checking this before a route is exactly what a real pilot does to catch a mismatch — a route filed VFR into what's actually IFR weather — before ever leaving the ground. This comes from NOAA’s free public Aviation Weather Center and is shown for reference only — it isn’t written into the exported .PLN, since MSFS’s flight-plan format has no field for weather at all.
![]()
Weather color reflects flight category: green for VFR, blue for MVFR.
While a lookup is in progress the line reads “Searching for weather...”, and it says so plainly if nothing comes back at all. If the airport itself has no current METAR, the nearest reporting station within about 50 nautical miles is used instead and labeled accordingly (e.g. “nearest: KXXX”). Hovering over either weather line decodes the raw METAR into plain English — station, observation time, wind, visibility, sky condition, temperature/dew point, altimeter setting, and common remarks like sea-level pressure and peak wind.
![]()
An airport with no METAR of its own falls back to the nearest reporting station.

How a SID, a STAR, and an approach fit together on a real IFR flight: SID out of the departure airport, en-route cruise, STAR into the destination area, then an approach down to a specific runway — landing, or flying the published missed approach and trying again.
What SIDs and STARs are, and why bother — A SID (Standard Instrument Departure) is a published procedure connecting an airport to the en-route airway structure right after takeoff; a STAR (Standard Terminal Arrival Route) is the arrival equivalent, connecting the en-route structure back down to an airport before you'd pick up an approach. Real IFR traffic flies these constantly — including in MSFS's own ATC — because they give a predictable, de-conflicted path in and out of busy airspace instead of a random string of waypoints. Adding one here does the same thing for your planned route: instead of guessing which fixes are actually flown near a busy airport and placing them by hand, the real published procedure, with its actual waypoint sequence, gets added for you.
4. Adding a SID or STAR — Once your departure (for a SID) or destination (for a STAR) resolves to a real airport, the Add SID... / Add STAR... buttons next to the Rwy: fields become active; click one to open the picker for that airport. First, pick a procedure from the Procedures list on the left — every published departure or arrival for that airport is listed by name. Next, check Runway Transition: if the procedure publishes a transition for the runway you already selected, it's filled in for you automatically (left blank if it doesn't publish one for any runway); if more than one runway transition is available, the field stays editable so you can pick a different one yourself instead of the automatic match. Then, if the procedure forks into more than one ending, choose which one you want from Enroute Transition. As you make these choices, Resulting Route updates live to preview the exact sequence of waypoints that will be added, so you know precisely what you're committing to before you do. The map previews it too — as you browse, the route redraws live right there, zoomed in tight on just that procedure's own fixes (even on a long cross-country route, it won't zoom out to show the whole thing, so the part that's actually changing stays easy to see); press Esc or Cancel and it reverts to whatever you had before, so nothing is final until you click Insert. This dialog doesn't lock up the rest of the window either — the map underneath stays fully interactive, so you can pan or zoom in yourself for a closer look while you compare options. When it looks right, click Insert — a SID goes in right after your departure, a STAR right before your destination — and nothing else can be inserted or dragged in between a procedure and the airport it belongs to, so the sequence always stays intact; click Cancel (or the X) instead to back out without changing your route. Waypoints added this way are highlighted in the Waypoints list so you can see at a glance which ones came from a procedure — a SID in gold, a STAR in blue-violet, so a STAR chained into an approach still reads as two distinct blocks instead of one solid color; changing (or clearing) the departure or destination airport automatically removes whichever procedure no longer applies. Hovering over any procedure-highlighted waypoint shows a tooltip with the full combination that produced it — the procedure name plus its runway and enroute transitions — so you can tell at a glance which one it was without reopening the picker. The picker opens with the procedure and transitions that best fit your runway and direction of flight already selected — see Auto Procedures below for how they are chosen. Add SID... and Add STAR... stay grayed out at an airport that doesn’t publish any, and Remove SID / Remove STAR only become available once one is on your route.

The Add SID... / Add STAR... buttons next to the Rwy: fields, active once a departure and destination airport (and runway) are entered.

The Select Procedure dialog: procedure list on the left, the matched runway transition and an enroute transition to choose from on the right, and the resulting route preview at the bottom.

The Waypoints list after inserting a SID: its waypoints get the gold highlight, alongside the normal per-kind text colors (airport, VOR/NDB, named fix).

A route with both a SID and a STAR added — the SID's waypoints in gold, the STAR's in blue-violet, so the two blocks stay easy to tell apart even without reading every row.
What an approach is, and how it fits with a SID/STAR — Everything so far gets you toward an airport, but none of it actually lines you up with a runway to land. A STAR only delivers you from the en-route airway structure down to a fix near the destination — that's as far as it goes. Getting from that fix down to a specific runway is a separate job, done by an approach (short for instrument approach procedure): a published, charted path flown at defined altitudes, ending at a Missed Approach Point — the point where you either have the runway in sight and land, or you don't and fly the published missed approach instead, a set escape routing back up to a safe altitude (often ending at a holding fix) so you can try again or divert elsewhere. Put together, a real IFR flight actually happens in this order: a SID gets you out of the departure airport, en-route cruise gets you across the distance, a STAR delivers you into the destination's local area, an approach takes you the rest of the way down to a specific runway, and you either land or fly the missed approach and try again. A STAR and an approach are not interchangeable — you need both, one after the other, any time visibility or clouds mean you can't just see the airport and fly straight to it. Different approaches exist for the same runway depending on what equipment guides them (ILS uses a precise ground-based radio beam, RNAV/GPS uses satellite navigation, VOR uses an older ground-based radio aid), so a busy airport typically publishes several for the same runway, and often more to other runways too.
5. Adding an Approach — Once your destination resolves to a real airport, the Add Approach... button next to the STAR buttons becomes usable; click it to open the approach picker for that airport. First, pick an approach from the Procedures list on the left — every published approach is listed by its own name (for example "I09C" for an ILS to runway 09C, or "H27LY" for an RNAV (RNP) approach to runway 27L). Next, if that approach has more than one starting point, choose which one you're arriving from under Transition (IAF) — the Initial Approach Fix, the specific point you'd join the approach from depending on which direction you're coming from; it's disabled when the approach doesn't fork by transition at all. Check Include missed approach if you want the published missed-approach fixes added on top of the final approach course too, for a fully complete route — most routes leave this unchecked, since a normal landing never actually flies it. Resulting Route updates live as you choose, so you can see exactly which waypoints will be added before you commit to anything. The map previews it too, the same as for a SID or STAR — redrawing and zooming live as you browse approaches, and reverting the moment you press Esc or Cancel. Click Insert to add it to your route — an approach always goes right before the destination airport, chained after any STAR you've already added rather than replacing it (the STAR delivers you to a fix; the approach picks up from there and takes you the rest of the way to the runway). Click Remove Approach to take it back off without reopening the picker; changing or clearing the destination airport removes it automatically, the same as it already does for a STAR. Approach waypoints get their own green highlight in the Waypoints list, distinct from a SID's gold or a STAR's blue-violet, so a STAR chained into an approach still reads as two separate blocks rather than one undifferentiated color. Hovering over one of these shows a tooltip with the approach name, its IAF transition, and whether the missed approach was included — the same hover detail a SID or STAR's own waypoints already give you. As with a SID or STAR, the picker opens on the suggested approach (see Auto Procedures), Add Approach... stays grayed out at an airport without published approaches, and Remove Approach only becomes available once one is on your route.

The Add Approach / Remove Approach buttons, next to the SID/STAR buttons.

The Select Approach dialog: procedure list on the left, the IAF transition and Include missed approach checkbox on the right, and the resulting route preview at the bottom.

Resulting Route with Include missed approach left unchecked — just the final approach course.

The same approach with Include missed approach checked — the published fixes past the runway are added too.
6. Importing a Flight Plan — Instead of building a route by hand, you can load one someone else already created — a SimBrief/Navigraph export, or any .PLN saved from MSFS’s own World Map. Click Import .PLN and pick the file, or drag a .PLN file from Windows Explorer and drop it onto the Flight Planner window or the Waypoints list. Either way, if a route is already in progress you’ll be asked to confirm before it’s replaced. The import pulls in the departure and destination airports, every resolvable intermediate waypoint (airports, VORs/NDBs, and named fixes that carry their own coordinates), cruising altitude, VFR/IFR, and departure/arrival runway where the file provides them — any waypoint it can’t match to a known airport or navaid is listed by name afterward rather than silently dropped. Plans you’ve opened or saved before are a click away: once there are any, Import .PLN opens a list of your ten most recent ones (hover one for its full path), with Browse for a .pln... at the top for any other file and Clear the list at the bottom.
7. Exporting the Flight Plan — Once your departure and destination are both resolved to real airports, click Export .PLN and save the file. The first time, the Save window opens in Documents\FlightLog Analyzer\Flight Plans; after that, wherever you saved last. When it’s saved, the file’s full path is copied to the clipboard, ready to paste into MSFS’s Load from this PC window (Ctrl+V in the File name box). This writes a standard MSFS flight-plan file with your departure, destination, and any intermediate waypoints (airports, VORs, NDBs, or plain map points) correctly typed, along with your chosen departure/destination runway if you picked one. For a step-by-step walkthrough of every screen you'll see loading that file into MSFS, see Appendix A: Loading a Flight Plan into MSFS 2024 at the end of this guide.
8. Flying It in MSFS — In Microsoft Flight Simulator, open the World Map, choose Load from PC under the flight plan options, and select the .PLN file you exported. MSFS loads the route onto its own map, ready to fly.
Flight Planner draws great-circle legs between the points you choose (the real shortest path over the globe, which can visibly curve on the map rather than looking like a straight line), with one exception: an inserted SID or STAR follows its actual published waypoint sequence instead of a straight line. Beyond that there’s no other aeronautical navdata behind it — no airways, no route validation — so it’s best thought of as a quick way to sketch a direct or VFR-style route with real departure/arrival procedures where you want them, not a full IFR dispatch tool.
Under the map, the Flight Planner shows your route from the side while you build it: the terrain along the whole route, each leg’s safe altitude, and your planned climb, cruise and 3° descent, with the Top of Climb and Top of Descent worked out from the real field elevations of your departure and destination airports. For the ideas behind it, see the chapter Vertical Profiles Explained.

Phoenix to Las Vegas at 12,500 ft: TOC 37.9 nm after KPHX, TOD 32.4 nm before KLAS, terrain along the route and each leg’s safe altitude (red), with the cruise clearing the route’s 12,400 ft SAFE ALT.
• The summary line — everything at a glance, for example:
ROUTE 980.4 nm CRUISE 12,500 ft TOC 37.9 nm after KPHX TOD 32.4 nm before KLAS SAFE ALT 12,400 ft
• ROUTE is measured exactly the same way as the Distance figure at the top of the planner, so the two always agree.
• The dashed amber line and the TOC/TOD markers mean the same as in the ATC View: the climb, the level cruise, the 3° descent, and the points where the climb ends and the descent should begin.
• Brown is the terrain along the route; the red line is each leg’s safe altitude, with the highest labeled (“SAFE 12,400”).
• Ticks and names mark each waypoint at its distance along the route.
• At the right end of the summary line — when there is room — the assumptions used (“300 ft/nm climb, 3° descent”) and the SCALE.
The strip redraws instantly whenever the route changes — adding, removing or dragging waypoints, changing the departure or destination, importing a .PLN, running Auto VOR Route or Auto Procedures, or changing Cruise Alt (ft). It even follows along while you browse choices in the SID, STAR and Approach pickers, so you can see how each procedure changes the route before you insert it. The terrain for a new or changed route takes a moment to load the first time; the summary line shows “(terrain loading...)” meanwhile, and “(terrain unavailable)” if it can’t be downloaded.
Try it — On the Phoenix–Las Vegas route, change Cruise Alt from 12,500 to 6,001. TOC moves from 37.9 to 16.2 nm after KPHX ((6,001 − 1,135) ÷ 300), TOD from 32.4 to 12.0 nm before KLAS ((6,001 − 2,181) ÷ 318) — and a red banner appears, because 6,001 ft is far below the route’s 12,400 ft safe altitude. The picture in Safe Altitude shows exactly that.
The same two points are marked on the map itself, as amber dots sitting right on the route line, labeled with the cruise altitude (“TOC 12,500 ft”) and “TOD”. Seeing them against real geography helps when planning: you can check where you will still be climbing as you cross a ridge, or which VOR or town you should be over when you start down. On a route too short to reach cruise, a single “TOC/TOD” dot marks the peak.
Move the mouse along the strip and a cursor line shows the distance along the route, the planned altitude, and — once the terrain has loaded — the ground and that leg’s safe altitude there. At the same time, a green dot appears on the map at that exact point of the route, labeled with the distance and planned altitude (for example “419.0 nm · plan 12,500 ft”) — the same hover-to-map link the ATC View and Mission Debrief have. Move the mouse off the strip and the dot disappears.
Because the strip’s scale starts just below the lowest point instead of at sea level, a route between high-elevation airports still fills the strip. It is also exactly where the safe-altitude check earns its keep:

Denver (KDEN, 5,431 ft) to Aspen (KASE, 7,820 ft) via the BLV VOR at 12,500 ft: TOC 23.6 nm after KDEN, TOD 14.7 nm before KASE — but the second leg crosses the Continental Divide, so SAFE ALT is 15,200 ft and the planner warns.
Raising Cruise Alt to 15,500 clears the warning (TOC then becomes 33.6 nm after KDEN, and TOD 24.2 nm before KASE).
A departure or destination dropped by clicking the map, rather than a real airport, has no field elevation on file, so FlightLog Analyzer plans from 0 ft at that end and says so in the summary line: “(300 ft/nm climb, 3° descent, 0 ft used for a non-airport end)”. The terrain along the route is still real. For realistic TOC and TOD numbers, start and end the route at real airports.
• Fewer than two points — the strip reads “Add a departure and destination to see the vertical profile”.
• Cruise altitude below the airports — for example 500 ft between two airports at 1,100 and 2,100 ft; the summary explains it (“Cruise altitude (500 ft) is below the airports”). Raise Cruise Alt and the plan appears.
Click the PROFILE tab (or anywhere on the strip’s top line) to fold the strip down to its summary line and give the map more room; click again to bring it back. The planner remembers which way you left it.
![]()
The Flight Planner’s profile strip folded down: the summary line stays visible.
If you’d rather not place every en-route waypoint yourself, Auto VOR Route... (the button with the VOR symbol, just below Navigation Database) plans the en-route part of your route as a chain of VORs — the classic way to navigate without airways or GPS: fly from one VOR to the next, always within reach of a station.
• It plans only the en-route part. The route runs from your departure — or, if you added a SID, from the SID’s last fix — to your destination — or, if you added a STAR or approach, to its first fix. Your SID, STAR and approach are left exactly as they are.
• Every leg stays within reception range. A VOR-to-VOR leg is only used if the two stations’ ranges meet in the middle, so you can switch from one to the next at the halfway point. The first and last legs must be within range of their VOR.
• It looks for the shortest such chain, with a small preference for fewer, longer legs over zig-zagging through every nearby station.
• Short trips go direct. If the start and end are 40 nm or less apart, no VOR is needed.
A VOR’s usable range depends on its class and on how high you are above it. FlightLog Analyzer uses the FAA’s standard service volumes (Aeronautical Information Manual 1-1-8), which every VOR of that class is guaranteed to meet:
|
T (Terminal) |
25 nm, from 1,000 up to 12,000 ft above the station. |
|
L (Low) |
40 nm, from 1,000 up to 18,000 ft above the station. |
|
H (High) |
40 nm up to 14,500 ft; 100 nm from 14,500 to 18,000 ft; 130 nm from 18,000 to 45,000 ft; 100 nm from 45,000 to 60,000 ft above the station. |
Each VOR’s class comes from the navigation database (terminal, low-altitude or high-altitude station). Because range grows with altitude, so does the freedom to fly straighter — a higher Cruise Alt usually means fewer VORs and a shorter route.
|
Note: In December 2020 the FAA introduced larger service volumes for many VORs (up to 70 nm above 5,000 ft), but the navigation data doesn’t say which stations were upgraded. FlightLog Analyzer uses the original volumes, which never claim more range than a station is guaranteed to have — so the routes it finds may use a few more VORs than strictly necessary, but never one you can’t receive. NDBs, military TACANs and RNAV-only stations are not used. |
1. Set up the route — Enter a departure and destination (and any SID, STAR or approach you want), and set Cruise Alt (ft) — the altitude decides how far each VOR reaches.
2. Click Auto VOR Route... — The route is worked out instantly and drawn on the map as a preview.
3. Read the summary — A dialog lists the chain of stations, the total distance, how much longer it is than flying direct, and — if your route already has en-route waypoints — how many it would replace.
4. Yes or No — Yes puts the VORs into your route (Undo takes them back out); No restores the route as it was.
5. Check the profile — The vertical profile and its SAFE ALT update for the new route. A VOR route follows radio coverage, not the terrain, so make sure your cruise altitude still clears it.
Phoenix (KPHX) to Las Vegas (KLAS) is 221.9 nm direct. Here is what Auto VOR Route finds at three cruise altitudes:
|
Cruise Alt |
Route found |
|
9,500 ft |
KPHX – PXR – BXK – DRK – IGM – LAS – KLAS: 278.7 nm (+25.6%). Below 14,500 ft even high-altitude VORs reach only 40 nm, so the route has to dog-leg west via Buckeye and north via Drake to stay in range. |
|
16,500 ft |
KPHX – PXR – EED – KLAS: 235.7 nm (+6.2%). Above 14,500 ft high-altitude VORs reach 100 nm, so Phoenix to Needles to Las Vegas works. |
|
24,000 ft |
KPHX – PXR – IGM – KLAS: 225.9 nm (+1.8%). Above 18,000 ft they reach 130 nm — almost a straight line. |
And a mountain example: Denver (KDEN) to Aspen (KASE) at 15,500 ft gives KDEN – BJC – RLG – DBL – KASE, 134.7 nm against 108.6 nm direct (+24.0%) — around the high terrain via the Kremmling (RLG) and Red Table (DBL) VORs.
If no chain of VORs connects the two points with every leg in range, nothing changes and the dialog explains why:
• “No chain of VORs reaches from start to end with every leg inside reception range at this cruise altitude.” — try a higher cruise altitude (high-altitude VORs reach much farther above 14,500 ft), or add a waypoint yourself to bridge the gap and calculate again from there.
• “There are no VORs with usable reception between these points at this cruise altitude.” — common over open ocean or in remote areas; plan those legs with waypoints or GPS instead.
|
Note: A calculated VOR route is a planning aid. It does not follow published airways or their minimum altitudes, and it doesn’t know about airspace, restricted areas or the weather. Always cross-check with the charts — the map’s IFR Low and VFR Sectional overlays are a good start. |
|
Note: The Flight Planner and Airport Heat Map windows no longer force themselves on top of the main window. Click the main window and it comes to the front, just like the ATC View and Mission Debrief windows — handy for glancing back at your logbook without moving the map out of the way. Minimizing the main window also no longer minimizes them along with it. |
Picking a SID, a STAR and an approach by hand means knowing which ones serve the runway in use, and which of them actually go your way. Auto Procedures... (the button with the wrench, just below Auto VOR Route...) does that for you: one click picks all three for the runways in the Rwy: boxes and your direction of flight, shows the result on the map, and adds it to your route when you say Yes.
The same logic also works quietly in the background: whenever you open Add SID..., Add STAR... or Add Approach..., the procedure it would choose is already selected for you, so even when you pick by hand, the usual case is just a click on Insert.
Note: Like the procedure pickers themselves, Auto Procedures works for U.S. airports only — see the note at the start of this chapter.
1. Set up the route — Enter a departure and a destination airport. If you want en-route waypoints, add them first (or run Auto VOR Route): the SID and STAR are chosen to connect with them.
2. Check the runways — Auto Procedures uses whatever is in the two Rwy: boxes. Normally they are already filled in with the runway best aligned with the current wind; choose another one if you know a different runway is in use, for example from the simulator’s ATIS.
3. Click Auto Procedures... — The choices are worked out instantly and the whole route, procedures included, is previewed on the map.
4. Read the summary — A dialog lists the runways (with the wind that chose them), then the SID, STAR and approach: the procedure, its transition, and how much distance it adds over flying direct. Anything it could not pick reads “none”, followed by the reason.
5. Yes or No — Yes adds all of them at once, replacing any SID, STAR or approach already on your route, and Undo (Ctrl+Z) takes the whole lot back out in a single step. No restores the route exactly as it was.
6. Fine-tune if you like — Every pick is an ordinary procedure on your route: open Add SID..., Add STAR... or Add Approach... to change one, or take it off with Remove SID / Remove STAR / Remove Approach.
Auto Procedures chooses the way a pilot would, in three steps: first the runway, then the procedures that serve that runway, then the one of those that goes your way.
1. The runway — The runway in the Rwy: box. When the planner fills that box in itself, it is the runway end pointing most directly into the wind reported in the airport’s METAR (or the nearest reporting station’s, when the airport has none of its own); with calm or variable wind, it is the longest runway. A runway you choose or type yourself is used exactly as it is.
2. Procedures that serve that runway — Many SIDs and STARs publish separate runway transitions — a version of the procedure for each runway it serves, named after the runway (RW26L, or RW26B for “both” parallel runways 26L and 26R). A procedure that has runway transitions is only considered if one of them is for your runway. A procedure without any serves every runway.
This is how an airport’s traffic flow comes into it. A busy airport uses its runways in one direction or the other depending on the wind — Atlanta in “east flow” or “west flow”, for example — and publishes different departures and arrivals for each. So when the runway changes, the procedures change with it, just as they would in the real world.
3. The one that goes your way — For every version still in the running (every procedure, with each of its transitions), Auto Procedures adds up how far you would actually fly: for a SID, from the departure airport through each of its fixes to the point your route heads for next; for a STAR, from the point your route arrives from, through each of its fixes, to the destination. It picks the version that adds the least distance compared with flying straight there. That one rule sends a westbound flight out on a departure to the west, and brings it in on the arrival from its own side of the airport.
Where “next” and “arrives from” are depends on your route:
• With en-route waypoints, the SID heads for the first of them, and the STAR comes in from the last.
• Without any, the SID and STAR aim at each other: the SID heads toward where the STAR begins, and the STAR comes in from where the SID ends.
• In the Add SID... / Add STAR... pickers, a procedure already on your route counts as part of it: with a STAR already added, the suggested SID heads for where that STAR begins.
• Runway transition: the one for your runway, as described above. Where a procedure publishes both an “all parallels” transition and one for your exact runway, either can be chosen — whichever fits your route better.
• Enroute transition: when a SID or STAR splits into several enroute transitions — different exits of a departure, or different entries of an arrival, each named after the fix where it begins or ends — one is always included, the one that best fits your direction, just as a real clearance names one (“the VRSTY3 departure, NOKIE transition”).
Sometimes every published procedure points somewhere else — typical on a short hop, where even the best SID leaves in the wrong direction or ends beyond your destination. Rather than send you on a long detour, Auto Procedures leaves a SID or STAR out when even the best one would add more than 20 nm plus 20% of the distance between your two airports: up to 40 nm on a 100 nm trip, up to 100 nm on a 400 nm trip. The summary names the closest fit and how far out of the way it would be, so you can still add it yourself if you want it.
Only approaches to your arrival runway are considered — circling approaches, which aren’t tied to one runway, are not. Among those:
• The best type first. In order of preference: ILS; IGS; GLS; RNAV (GPS); GPS; LOC; LDA; SDF; RNAV (RNP); LOC back course; VOR/DME; VOR; TACAN; NDB. When a runway has an ILS, the ILS is used. RNAV (RNP) comes after the localizer-based types because, in the real world, many of those approaches need a special authorization.
• Joined to your STAR. If one of the approach’s fixes is where your STAR ends, the approach is joined right there — that is what the arrival was designed to lead into — and the approach’s fixes before that point are not added a second time.
• Otherwise, the closest way in. An approach often has several initial approach fix (IAF) transitions, one for each direction of arrival. The one giving the shortest path from where your route arrives is used. The version without a transition — starting at the intermediate fix, where in real life ATC would vector you onto it — is used only if it is more than 10 nm shorter.
• Same type twice. When a runway has two approaches of the same type (an ILS Y and an ILS Z, say), the one that fits your route better is used.
• No missed approach. The published missed approach is not added. If you want it on your route, open Add Approach... and check Include missed approach.
Atlanta (KATL) to Orlando (KMCO), with no en-route waypoints. With the wind favouring runway 10 at Atlanta and 18L at Orlando, the summary reads:
Runways: 10 (wind from 140°) out of KATL, 18L (wind from 250°) into KMCO
SID: VRSTY3 -- runway 10, NOKIE transition, +5 nm over flying direct
STAR: GRNCH5 -- COAXE transition, runway 18L, +4 nm over flying direct
Approach: RNAV (GPS) 18L (R18L) -- from ZANTI
VRSTY3 is one of Atlanta’s east-flow departures, and NOKIE is its exit toward Florida. GRNCH5 brings you into Orlando from the north, with a runway transition to the 18 runways. Orlando has no ILS to 18L, so the RNAV (GPS) approach is used, starting at its ZANTI initial approach fix.
Now change the arrival runway to 18R, and the approach becomes the ILS 18R — joined to the GRNCH5 arrival at YAGGO, the fix where the arrival ends. Turn both runways around — 26R at Atlanta, 35R at Orlando — and everything changes: SMLTZ3, one of Atlanta’s west-flow departures (a little longer, since a westbound takeoff has to turn back toward Florida); SHREK2, because GRNCH5 only serves Orlando’s 17 and 18 runways; and the ILS 35R.
Add SID..., Add STAR... and Add Approach... use exactly the same logic. When a picker opens, the suggested procedure and its transitions are already selected and previewed on the map, so you can simply click Insert — or browse the others first. A line under Resulting Route explains the choice:
• “Suggested: VRSTY3 -- runway 10, NOKIE transition, +5 nm over flying direct” — the suggestion, and why.
• “No suggestion -- …” — nothing fits, with the reason (the same reasons as in Messages You Might See below). The picker then opens on the first procedure in the list.
• “Showing the GRNCH5 already on your route.” — when your route already has a procedure of that kind, the picker opens on that one, so you can adjust it; the suggestion is still shown above.
Suggestions in the pickers fit around what is already on your route: the suggested approach joins the STAR you actually added, and the suggested SID heads for where your STAR begins. (Auto Procedures, which replaces all three at once, ignores the ones already there.)
• Add SID... is available only when the departure airport publishes at least one SID; Add STAR... and Add Approach... only when the destination publishes at least one STAR or approach. At airports outside the U.S., and at small fields without published procedures, they stay grayed out.
• Remove SID, Remove STAR and Remove Approach are available only while that kind of procedure is on your route.
• Auto Procedures... needs a departure and a destination airport, at least one of which publishes procedures.
Auto Procedures chooses by runway and by the shape of the route — the information the navigation data contains. Real controllers also go by things that aren’t in it: which runways the airport is actually using right now (announced on the ATIS), procedures restricted to jets or to propeller aircraft, noise-abatement rules, other traffic and the time of day. So the procedures it picks are sensible ones for your route, not necessarily the ones real ATC would hand you.
Note: The simulator’s own ATC chooses its runway from the simulator’s weather. If that differs from the real-world METAR — with live weather off, say — the simulator may assign a different runway and procedures. Set the Rwy: boxes to the runway the simulator is using, and Auto Procedures will match it.
• “No procedures could be picked.” — none of the three could be chosen; the reason for each is listed underneath.
• “… has no SIDs in the navigation database” (or STARs, or approaches) — the airport doesn’t publish any. It is outside the U.S., or a field without instrument procedures.
• “no runway selected for …” — choose a runway in that airport’s Rwy: box first.
• “… publishes no SIDs for runway …” (or STARs, or approaches) — all of the airport’s procedures of that kind are for other runways. At a busy airport this usually means that runway isn’t used in that direction for departures (or arrivals); try the runway the airport’s current flow uses.
• “the closest fit (…) would add … nm, too far out of the way for this flight” — see Too Far Out of the Way above.
• “add a destination first, so the direction of flight is known” — the Add SID... picker can’t suggest a SID until it knows where you are heading.
• “the route doesn’t start at an airport” (or end) — the departure or destination is a point you clicked on the map, which has no procedures.
• “… waypoint(s) couldn’t be found and will be skipped: …” — a fix in the procedure isn’t in the navigation database; the rest of the procedure is still added.
• “The navigation database has no published procedures for … or ….” — neither airport publishes any procedures — usually because both are outside the U.S.
Note: Auto Procedures is a planning aid. Always check the procedures against the current charts before flying them, especially at an airport you don’t know.
Not sure where to fly next? Surprise Me (the Surprise Me... button with the dice on it, at the top left of the Flight Planner beside VFR / IFR) picks a destination for you: by default an airport you have never flown into, within the distance you choose, with a runway your aircraft can use. One more click puts it on your route — as a simple VFR flight, or as an IFR flight complete with a SID, a STAR and an approach.

The Surprise Me... button, at the top left of the Flight Planner beside VFR / IFR.

Surprise Me: an IFR flight from Los Angeles (KLAX) with a SID, a STAR and any type of approach — Waterbury-Oxford (KOXC), about 13 hours away at 168 kt, is one of 315 airports that fit.
1. Click Surprise Me... — The Surprise Me window opens, starting from your route’s departure airport — or, with none entered yet, from where your last logged flight landed. To start somewhere else, type another airport in From, or click the circular arrows beside it for a random airport nearby (within 2,000 nm of the one the window opened with; for an IFR flight, one with a SID). With Only airports I’ve never flown out of ticked, it skips every airport your logbook has taken off from.
2. Set the range — Distance is how far the destination may be, in nautical miles, up to 6,000 nm. Runway at least and Paved only make sure the airport has a runway your aircraft can use. Only airports I’ve never flown into leaves out every airport your logbook has already landed at, touch-and-gos included.
3. Choose VFR or IFR — VFR is just that: any airport that fits. IFR lets you ask for procedures at each end. Under Departure, SID means the departure must publish one (the circular arrows only pick airports that do). Under Destination, you can tick STAR and Approach — and for the approach, the types you would accept (ILS, LOC, RNAV (GPS), VOR, NDB). With a STAR or an approach ticked, only destinations that publish one are offered. Choices that don’t apply (the procedures, on a VFR flight) are grayed out.
4. Click Surprise me — The pick appears below: the airport, how far it is and roughly how long it takes at the planner’s cruise speed, the course to it, its longest runway, and — for IFR — how many STARs it has and which types of approach. Another picks again, never the same airport twice in a row.
5. Click Use this flight — Your route is replaced by a direct flight between the two airports, set to VFR or IFR to match. Undo (Ctrl+Z) brings back the route you had before.
6. For IFR: the procedures — The window stays open for a moment while the weather loads at both airports — the wind picks the runways, and the runways the procedures. Then the Auto Procedures summary appears, for just the procedures and approach types you ticked, with the result previewed on the map. Yes adds them to your route; No keeps the direct flight. Either way, the map then zooms to the whole flight.

The follow-up for KLAX to KOXC: the runways from the wind at each airport, then the SID, STAR and approach picked for them.
Your settings in the Surprise Me window are remembered, even after you close FlightLog Analyzer, so the next surprise starts where the last one left off.
Every procedure Surprise Me adds is an ordinary one on your route: change it with Add SID..., Add STAR... or Add Approach..., or take it off with Remove SID / Remove STAR / Remove Approach. See Auto Procedures above for how they are chosen.
Surprise Me only offers flights it can actually build for you, so a few rules decide which airports can come up:
• Procedures are U.S. only. The SIDs, STARs and approaches come from the FAA, the same data as Add SID..., Add STAR... and Add Approach..., so only U.S. airports have them.
• IFR departures need a SID. With SID ticked, the departure must publish one: an airport without SIDs (1Z1, say) is turned down with a message. The circular arrows, on an IFR flight, only ever pick an airport that has one.
• STAR and Approach narrow the destinations. With STAR ticked, a destination must publish a STAR; with Approach ticked, an approach of one of the types you ticked. With both, it needs both — which keeps the flight in the U.S.
• IFR abroad. Untick STAR and Approach, and a U.S. departure with a SID can go anywhere in the world: the destination doesn’t need procedures of its own. A VFR flight can go anywhere, with no procedures at all.
• Distance. A destination can be up to 6,000 nm away, measured straight (along the great circle) from the departure. The circular arrows pick a departure within 2,000 nm of the airport the window opened with.
• Flight time is a rough guide. It’s the straight-line distance at the planner’s cruise speed: no wind, no climb, no procedures. Surprise Me doesn’t know your aircraft’s range or fuel, so check the planner’s Fuel line before you fly a long one.
• Runways. Runway at least and Paved only ask for at least one runway that long (and paved). The runway you’ll use is picked afterwards by the wind, so check it in the Rwy box.
• The approach is for the runway in use. A destination is offered when it publishes one of your approach types for any runway, but the approach added is for the runway the wind favors. If that runway has none of your types, no approach is added, and the summary says so.
• A SID or STAR that goes too far out of the way is left out. When every published one would add more than 20 nm plus a fifth of the flight’s distance, the summary says none fits.
• Weather. The runways come from each airport’s real-world weather report (METAR). Surprise Me waits up to 15 seconds for both; an airport with no report keeps the runway already in its Rwy box.
• Never flown into / out of. These go by your logbook the way Places Flown does: flown into means landed there, touch-and-gos included; flown out of means took off from there. A departure you type into From yourself is always allowed.
A few small checks a pilot makes before every flight, worked out for you as you plan — no extra windows, just a line of text where you’d look for it.
In the US, the altitude you cruise at depends on which way you’re going (the hemispheric rule). By magnetic course:
• 0° to 179° (eastbound): VFR at odd thousands + 500 ft (3,500, 5,500, 7,500 …); IFR at odd thousands (5,000, 7,000 …).
• 180° to 359° (westbound): VFR at even thousands + 500 ft (4,500, 6,500 …); IFR at even thousands (4,000, 6,000 …).
When your Cruise Alt (ft) doesn’t follow the rule, an orange hint appears next to it with the nearest correct altitude below and above — for example Eastbound VFR: 7,500 or 9,500. Click either altitude to use it. Hover the hint to see your course in degrees magnetic.
• The course is the direct course from your departure to your destination, converted from true to magnetic with the local magnetic variation.
• The VFR rule applies more than 3,000 ft above the ground and below 18,000 ft (class A, where VFR isn’t allowed); the planner uses the departure airport’s elevation for the ground. The IFR rule is checked up to FL410.
• Switching between VFR and IFR (the button at the top left) updates the hint straight away.
Under each Rwy: box, a short line shows what the airport’s current wind does on that runway — for example Head 12, cross 5 L, with (G22) when it is gusting. It updates when the METAR arrives and whenever you choose a different runway.
• Head / Tail is the wind along the runway; cross is the wind across it, with L or R for the side it comes from.
• Orange means take note: a tailwind, or a crosswind of 15 kt or more (steady or in the gusts).
• Hover the line for the details: the wind direction in degrees true and magnetic, its speed and gusts, and the head and crosswind in the gusts.
• Wind calm and Wind variable appear when there is no single direction to work with.
Note: A METAR reports the wind in degrees true, while a runway’s number is its magnetic heading. The planner converts the wind with the local magnetic variation before working anything out — including the runway it suggests from the wind, which can now differ slightly from earlier versions at airports with a large variation.
The Fuel figure on the Distance / Time / Fuel line now shows the trip fuel and, in brackets, what to load with the legal minimum reserve added:
Fuel: 70.8 gal (77.8 w/ reserve)
• IFR: 45 minutes at your fuel burn (14 CFR 91.167).
• VFR: 30 minutes by day (91.151) — 45 at night, which the planner can’t tell, so plan the extra yourself for a night flight.
• The reserve is a fixed amount of time, so it doesn’t change with the route or the wind; the trip fuel does, and so does the total. Hover the line to see the reserve on its own.
Copy Route, next to the Waypoints: title, copies your route as one line of text — ready to paste into SimBrief, a VATSIM flight plan or a forum post. For example, after Auto Procedures from Atlanta to Orlando:
KATL VRSTY3 NOKIE COAXE GRNCH5 KMCO
• The SID and STAR are written by name, together with the fix where the route joins them, the way a filed route names them. The approach isn’t part of a filed route, so it’s left out.
• Airports, VORs, NDBs and named fixes appear by their identifiers. A point you clicked on the map is written as a latitude/longitude point in the standard flight-plan form — for example 3439N11225W.
• The link briefly reads Copied! when it’s done; hover it afterwards to see what was copied.
Your logbook already knows how you flew a route last time. When the Flight Planner’s route starts and ends at airports, it checks your logbook for every earlier flight between those two airports and, if it finds any, shows them right on the planner map: a FLOWN BEFORE panel listing the flights, and each flight’s actual path drawn on the map in its own color. Before you plan a route again, you can see exactly how you flew it before — which way you went around the mountains, where you joined the approach, how long it took and in which aircraft.

The Flight Planner with the FLOWN BEFORE panel open: two earlier Phoenix–Sedona flights drawn in orange and light blue under the planned route (dashed).
• Flights between the same two airports, in either direction. Planning Phoenix (KPHX) to Sedona (KSEZ) also finds your flights from Sedona to Phoenix — they are marked “flown the other way”. Airport codes match with or without the US “K” prefix, so a logbook entry of PHX matches a route from KPHX.
• Every flight in your logbook, not just the ones the main window’s filters currently show.
• Newest first, up to 10 on the map. If you have flown the route more often, the panel says how many there are in total and that the newest 10 are shown.
• Only when both ends are airports. If your route starts or ends at a point you clicked on the map, there is nothing to match, and the panel stays hidden. It also stays hidden when you have never flown between the two airports.
The panel slides out from the top-right corner of the map. Each row is one earlier flight:

The FLOWN BEFORE panel: one row per earlier flight, with its color on the map.
• The checkbox shows or hides that flight’s track on the map.
• The colored line is the color of that flight’s track on the map.
• First line: the date it was flown and the aircraft.
• Second line: the flight time and distance, plus “flown the other way” for a flight from your destination to your departure, or “no track recorded” when the logbook has no positions for it (its checkbox is then grayed out).
• Use plan and Use track load that flight into the planner — see Fly It Again below. Use plan only appears for flights that have a saved flight plan; Use track only for flights with a recorded path.
Each track is the path the aircraft actually flew — from FlightLog Analyzer’s telemetry when it recorded the flight (detailed and exact), otherwise from the positions the simulator’s own logbook keeps (coarser, but still the real path). The tracks are drawn underneath your planned route line, so the plan always stays on top.
• Hover over a row to make its track thicker and bring it to the front — handy when several flights overlap.
• Hover over a track to see which flight it is: the date, aircraft, flight time and distance.
• Clicking a track does nothing else — it won’t add a waypoint where you clicked, the way clicking the map normally does.
Click the FLOWN BEFORE tab on the panel’s left edge to fold the panel away; click it again to bring it back. While the panel is folded, the tracks are hidden too, and the tab shows how many flights it found — “FLOWN BEFORE (3)”. The planner remembers which way you left it.

Folded away: only the FLOWN BEFORE tab remains, with the number of flights found.
Fly It Again takes a flight from your logbook and loads it straight into the Flight Planner, ready to look over, change and export as a .PLN for the simulator. It is the quickest way to repeat a trip you enjoyed, practice the same approach again, or fly yesterday’s route in a different aircraft.
There are two very different ways to fly a flight again, and it is worth understanding the difference before you choose: The Planned Route gives you the flight plan you had loaded when you flew it; The Route Actually Flown gives you the path the aircraft really took. They can be the same — or quite different, if you were vectored, took a shortcut, flew a detour around weather, or simply flew without a plan.
|
|
The Planned Route |
The Route Actually Flown |
|
Comes from |
The flight plan that was loaded in the simulator during the flight, saved with the flight’s telemetry. |
The path the aircraft actually flew: telemetry if recorded, otherwise the simulator logbook’s positions. |
|
Waypoints |
The same named waypoints (fixes, VORs, NDBs, airports) in the same order, at their saved positions. |
Up to 20 map points (WP1, WP2, …) where the path turned. No names — they are just positions. |
|
SID, STAR, approach |
Put back as real procedures — tinted in the waypoint list and removable with Remove SID / STAR / Approach. |
Not included. A big turn the SID or STAR made may show up as a map point, but not as a procedure. |
|
Around the airports |
Everything in the plan, right to the destination. |
Nothing within 3 nm of either airport — taxiing, the traffic pattern and the final approach are left out. |
|
Cruise altitude |
The plan’s cruise altitude (flights flown with version 3.4.0.0 or later), otherwise the level you cruised at. |
The plan’s cruise altitude (version 3.4.0.0 or later), otherwise the level you cruised at. |
|
Available for |
Flights recorded by FlightLog Analyzer’s telemetry while a flight plan was loaded in the simulator. |
Any flight with a recorded path — which is almost every flight in your logbook. |
From the logbook — Right-click a flight in the main window and choose Fly It Again (open in Flight Planner), then The Planned Route or The Route Actually Flown. The Flight Planner opens (or comes to the front if it is already open) with the route loaded. Select just one flight; The Planned Route is grayed out when no flight plan was saved with that flight.
From the FLOWN BEFORE panel — Click Use plan or Use track on any row. These do exactly the same as the two menu choices.
Replacing your current route — If the planner already has a route, you are asked first: “Load the route you planned for this flight? It replaces your current route (Undo brings it back).” Undo (Ctrl+Z) really does bring your previous route back in one step. Note that the planner automatically reloads the last .PLN you used when it opens, so you may see this question even when you opened the planner just for Fly It Again.
After loading — The loaded route behaves like any other: edit it, add or remove waypoints and procedures, check the vertical profile and terrain, then Export .PLN to fly it in the simulator. The original flight in your logbook is never changed.
|
Note: Fly It Again is part of the Flight Planner, which is a Pro feature (also available during the trial period). |
Whenever FlightLog Analyzer records telemetry for a flight, it also saves the flight plan that was loaded in the simulator at the time — whether it came from the World Map, the EFB, SimBrief, or a .PLN exported from FlightLog Analyzer’s own planner. The Planned Route rebuilds your route from that saved plan:
• Departure: the plan’s departure airport (for flights flown with version 3.4.0.0 or later), otherwise the departure airport in your logbook.
• Waypoints: every waypoint the plan had, in the same order and at the same positions. The simulator’s own traffic-pattern points (the ones it adds for a VFR departure or arrival) are left out — they aren’t real waypoints and couldn’t be exported.
• Destination: the plan only saved the destination’s position, so FlightLog Analyzer names it after the destination airport in your logbook when that airport is within 3 nm of it. If the plan ended somewhere else — a point you chose on the World Map, say — the route ends at a map point called DEST instead.
• Cruise altitude: as described in the table above.
This needs a little explanation, because the information is split between two places, and neither has all of it:
• The saved flight plan has every waypoint — including the ones that came from your SID, STAR and approach — but it doesn’t say which waypoints belonged to which procedure. To the plan, BCE, HOLDM and AALAN are just three waypoints in a row.
• The simulator’s logbook records the names of the SID and STAR you flew and the type and runway of the approach (for example “ILS-26L”), but not their waypoints.
Fly It Again puts the two together. For each procedure the logbook recorded, it looks the procedure up in FlightLog Analyzer’s navigation database, works out every version of it (each runway and enroute transition for a SID or STAR, each initial approach fix for an approach, with and without the missed approach), and looks for the version whose waypoints line up with the start of your plan (a SID) or the end of it (the STAR and approach). Only a real match counts: at least two waypoints in the procedure’s own order. A waypoint name alone is never enough to call something a procedure.
Each recorded procedure then ends up one of three ways — and a message after loading tells you which, procedure by procedure:
|
1. Found in your saved plan |
The waypoints in your plan that match are marked as that procedure, exactly as they were planned — nothing is moved, added or removed. They get the procedure’s tint in the waypoint list, and Remove SID / Remove STAR / Remove Approach work on them just as if you had added the procedure yourself. This is the usual case when the procedure was part of the flight plan you loaded. |
|
2. Not in your saved plan |
If the logbook recorded a procedure but its waypoints aren’t in the saved plan, the procedure is added from the navigation database, in the right place: a SID after the departure, a STAR and approach before the destination. The runway transition is the runway you used, and the route joins the procedure where your plan already reaches it when it can. This is today’s version of the procedure, which may be different from the one you flew if it has been revised since — the message says so. |
|
3. Not in the navigation database |
If the procedure isn’t in the navigation database at all (it may have been withdrawn or renamed, or it is a custom one), nothing is added, and any of its waypoints in your plan stay as ordinary waypoints. You can add a current procedure yourself with Add SID / Add STAR / Add Approach. |
A flight flown without a SID, STAR or approach simply loads as its plan, with no message.
Say you flew Phoenix (KPHX) to Las Vegas (KLAS) with the BALDY3 departure, the BLAID2 arrival and the ILS approach to runway 26L, and your saved plan was:
KPHX GILAA ADYAN MAXXO ACH … BCE HOLDM AALAN CHOWW BLAID BERBN BISHP HOGOG KODSE HUXAR RELIN RW26L KLAS
The logbook recorded SID BALDY3, STAR BLAID2 and approach ILS-26L. Choosing The Planned Route finds all three in the plan, and the message after loading reads:
Loaded the route you planned for your flight on 2026-09-21.
• Approach ILS-26L (I26LY): found in your saved plan -- 7 waypoint(s) marked as the approach, exactly as planned.
• STAR BLAID2: found in your saved plan -- 5 waypoint(s) marked as the STAR, exactly as planned.
• SID BALDY3: found in your saved plan -- 4 waypoint(s) marked as the SID, exactly as planned.
GILAA to ACH are now your BALDY3 departure (ACH transition), BCE to BLAID your BLAID2 arrival (BCE transition), and BERBN down to the runway your ILS 26L approach — each tinted in the waypoint list, just as if you had picked them with Add SID, Add STAR and Add Approach. (I26LY is the navigation database’s own name for that ILS approach.)
Now say the same flight’s plan had stopped at the en-route waypoints — no arrival or approach in it. The message would read:
• Approach ILS-26L: its waypoints weren't in your saved plan, so I26LY was added from the navigation database (today's version, which may differ from what you flew).
• STAR BLAID2: its waypoints weren't in your saved plan, so it was added from the navigation database (today's version, which may differ from what you flew).
— and the route would end with the BLAID2 arrival (AALAN CHOWW BLAID) and the final part of the ILS 26L (HUXAR RELIN RW26L), added from the database. Because the plan didn’t reach any of the arrival’s transitions, only the parts every transition shares were added; you can choose a different transition afterwards with Add STAR or Add Approach.
|
Tip: If the message says a procedure was added from the navigation database, glance at the route on the map before you fly it. Procedures are revised from time to time, and the current version may not be quite the one you flew. |
The Route Actually Flown ignores the plan and rebuilds the route from where the aircraft really went. That makes it the one to use for a flight you flew without a plan, flew off-plan (vectors, shortcuts, a scenic detour), or one from before FlightLog Analyzer saved flight plans.
• The path: FlightLog Analyzer’s telemetry when it recorded the flight, otherwise the positions the simulator’s own logbook keeps. (Telemetry you have disabled for a flight isn’t used.)
• Boiled down to the turns: a recorded path has hundreds or thousands of points. Fly It Again keeps only the ones where the path actually changed direction by more than about half a mile, up to 20 of them — the most important turns first — and adds them as map points WP1, WP2 and so on. A straight leg becomes one leg; a dog-leg around a mountain keeps its corner.
• The airports are left to the airports: points within 3 nm of the departure and destination are dropped, so taxiing, the traffic pattern and the final approach don’t turn into waypoints. The route starts and ends at the departure and destination airports themselves (or at the path’s first and last points, if an airport isn’t in the airport database).
• No procedures: the path only knows positions, not names, so SIDs, STARs and approaches are not recreated. Add them with Add SID, Add STAR and Add Approach if you want them.
• Cruise altitude: the plan’s cruise altitude when one was saved, otherwise the altitude you spent most of the top part of the flight at, rounded to the nearest 500 ft.
Example: a scenic flight from Prescott (KPRC) to Cottonwood (P52) that wandered north past Jerome loads as KPRC, a few map points following the way you went around the hills, and P52 — rather than the straight 19.5 nm line between the two airports.
• To fly the same IFR route again, procedures and all — The Planned Route.
• To repeat a VFR sightseeing trip the way you actually flew it — The Route Actually Flown.
• If you were vectored or took a shortcut and want the original plan — The Planned Route.
• For an older flight, or one flown without a flight plan — The Route Actually Flown (The Planned Route isn’t available).
Either way, it is a starting point: everything can be edited afterwards, and Undo takes you back to where you were.
• “No flight plan was recorded with this flight, so there’s no planned route to load.” — FlightLog Analyzer wasn’t recording telemetry, or no flight plan was loaded in the simulator, when this flight was flown. Use The Route Actually Flown instead.
• “This flight’s departure airport (…) isn’t in the airport database, so its planned route can’t be rebuilt.” — the departure can’t be placed on the map. Use The Route Actually Flown, which starts from where the flight really started.
• “This flight has no recorded track, and its departure and destination airports aren’t both in the airport database, so there’s no route to load.” — there is nothing to build a flown route from. This is rare; it happens with some imported flights.
Every flight tells a story, and Mission Debrief lets you watch it again. Was that approach really stable? Where exactly did you float past the touchdown zone? How hard did you hit, and why? Replay the whole flight at up to 120× speed, jump straight to the takeoff, the touchdown or the hardest G, and see the answers on the map and the profile instead of in a pile of numbers. It’s the debrief a flight instructor would give you, after every single flight.
Where the ATC View tracks your active flight in real time, Mission Debrief brings the same precision to your historical flights — letting you relive and analyze every moment after the wheels are down.
Mission Debrief uses the same map, HUD, and altitude-profile layout as the ATC View, with one key difference: every parameter, overlay, and color-by mode can be selected independently of the original flight. You can re-examine a flight in MSL coloring even if you flew it watching AGL, or pull up the IFR Low chart over a flight you originally flew on a VFR sectional.
Beyond the map, it can play the flight back at up to 120× speed, mark the moments worth a second look (takeoffs, touchdowns, top of climb and descent, the highest G), report on every landing — how hard, where on the runway, and whether the approach was stabilized — compare the flight with your other flights of the same route, show your personal bests on that route, and line up all your landings on a runway side by side. Each has its own section below.
|
Note: Mission Debrief is available only for flights that captured SimConnect telemetry. Requires a PRO license once the trial period ends. |
To open Mission Debrief, right-click any flight that captured telemetry and choose Mission Debriefer.

Right-click context menu showing Mission Debriefer option
When a replay is loaded, the map enters HUD Replay Mode:
• The flight track is rendered with an amber color shift to make it visually distinct from a live ATC View track.
• A ⌛ HISTORY badge appears in the corner as a constant reminder that you're viewing recorded data rather than a live flight.
• The HUD shows telemetry values from the recorded data, scrubbable via the replay controls. WIND and FUEL show -- on flights recorded before FlightLog Analyzer 3.4.5.0, which didn’t record them yet. Flights recorded before 3.4.6.0 show FUEL in gallons, even in a jet.
•

Mission Debrief in HUD Replay Mode
Mission Debrief faithfully reconstructs your planned route during playback, including all intermediate fixes that were active when the flight was recorded. The destination lines, the bearing/distance midpoint labels, the waypoint sequencer, and the navigator counter at the bottom of the map all behave exactly as they did during the live flight.
|
Note: The same first-flight MSFS bug applies here: if a flight was recorded as the first flight after starting MSFS, the en-route waypoints will be missing from its replay too. The destination is still shown, but the route between origin and destination will be plotted without the intermediate fixes. |
All of the ATC View's map controls are available in Mission Debrief: the aviation chart overlays (IFR Low/High, VFR Sectional, etc.), the opacity slider, and all color-by modes (AGL, MSL, true airspeed, ground speed, G-load, vertical speed, sim rate). Change them freely — you're not bound to whatever you had configured during the original flight.
Just as in the ATC View, hovering the mouse over the altitude profile marks the corresponding point on the map and switches the HUD into history-mode display for that moment in the flight. This is the fastest way to find peak G-events, maximum altitudes, or specific points along the route. A second line on the profile (see A Second Line on the Profile) works here too.
Press Play in the bar at the top of the map and Mission Debrief replays your flight: the aircraft moves along its track, and the HUD, the profile’s cursor, the waypoint navigator and the destination lines follow it — exactly as when you hover the profile.

The playback bar: back to the start, play / pause, the speed, and how far into the flight you are.
• Buttons — the first goes back to the start of the flight; the second plays and pauses. Space plays and pauses too, once you’ve clicked the map.
• Speed — 1× plays the flight in real time; 5×, 20×, 60× and 120× speed it up. FlightLog Analyzer remembers your choice.
• Clock — how far into the flight you are, and the flight’s total length.
• Dull stretches skipped — a stop of more than ten seconds (parked, holding short, or with the sim paused) plays in about a second, and any gap of more than two minutes in the recording in two, so playback doesn’t wait through them in real time.
• The map follows — when the aircraft nears the edge of the view, the map moves with it.
• Jumping around — click the profile to jump to that point. While playing, hovering the profile does nothing, so it doesn’t fight the playback; while paused, hovering works as usual, and Play continues from the last point you clicked.
Mission Debrief marks the moments worth a second look with a small labeled badge on the map and a matching tick on the profile. Hover a badge to see what happened and when; click it — or click the profile at a tick — and playback jumps to that moment. The events are worked out from the flight’s recorded telemetry, so they appear for older flights too.

Event badges on the track and ticks on the profile: the takeoff, a sim-rate change (4×) and the highest G.
• T/O — each takeoff: the last moment on the ground before climbing away.
• TD and B — each touchdown and bounce, ticked on the profile (the map already shows them as landing-report markers). For flights recorded before landing reports existed, the profile marks each landing from the telemetry instead.
• TOC and TOD — where you reached cruise and where you started down, shown only when there was a real cruise: at least five minutes near the flight’s highest altitude, more than 2,000 ft above the ground. These are where you actually flew them; the route profile’s own amber TOC/TOD marks the plan’s.
• Pause — the sim paused (or the aircraft sat still) in the air for 20 seconds or more, with how long.
• Sim rate (4×, 1× ...) — each change of simulation rate.
• Highest G — the highest G-load in the air, when it reached 1.3 G or more (the G at touchdown is in the landing reports).
• α (angle of attack) — the highest angle of attack in the air, for flights that recorded it.
Flown this route before? Mission Debrief can lay another of those flights over the one you’re looking at. The Compare dropdown on the playback bar (top center, after the flight clock) lists your other flights from the same departure airport to the same destination airport, newest first. Flights flown the other way round aren’t listed: they climb out of and land at different airports, so there is nothing like-for-like to compare. The dropdown appears only when there is at least one such flight; choose Compare: Off to remove a comparison. When you pick a flight, the map zooms out to show both flights and the compared track blinks a few times, so you can spot it at once.
How much you can compare depends on one thing: whether the other flight was recorded with telemetry — that is, whether FlightLog Analyzer was running during it, recording its position, altitude, speed and more every second. Those flights are listed normally. Flights flown before you used FlightLog Analyzer, or while it wasn’t running, are marked (map only).

Comparing two recorded flights of the same route, paused mid-flight: the other flight’s track (dashed, colored by altitude), its labeled ghost dot, and its line and “vs” readout on the profile.
• On the map — its track appears dashed, with a magenta edge so it never reads as your own. When Color Track By is set (MSL, True Speed and so on), it is colored on the same scale as your track, so the same color means the same altitude or speed on both; with No Coloring it is plain magenta.
• Ghost dot — as you hover the profile or play the flight back, a magenta dot shows where the other flight was at that moment, labeled with its altitude and speed and how they compare with yours, for example “186 ft higher · 9 kt slower”.
• On the profile — its line appears dashed in magenta, in the same mode and on the same scale as yours, and the hover readout adds its value (“vs 1,464.5 ft”) under your own.
The two flights are lined up at takeoff: everything compares the same number of seconds after each flight’s own takeoff, so a longer taxi doesn’t throw it off. Only the part of the other flight that overlaps this one’s timeline appears on the profile, and nothing of it is drawn on the profile in Profile: Route (Vertical), whose strip runs by distance along the route rather than through time.
For a flight without telemetry, all FlightLog Analyzer has is what MSFS itself kept in its logbook: a series of positions with altitudes, but no reliable timing between them. That is enough to draw where the flight went, but not to say where it was at any particular moment. So:
• On the map — its track appears dashed, as above. With Color Track By set to MSL it is colored by its altitude on your flight’s scale (any logbook altitude that is clearly wrong is left out); with any other setting it is plain magenta, because the logbook keeps no speeds, vertical speeds, G or angle of attack.
• No ghost dot, no profile line and no “vs” readout — with no clock to line it up with your flight, there is no “at this moment” to compare.
In short: a map-only comparison shows whether you flew the same ground track and roughly how high; a comparison with telemetry also shows how you flew it — higher or lower, faster or slower, moment by moment.
When you have flown a route more than once — the same departure airport to the same destination — Mission Debrief shows a small PERSONAL BESTS panel just under the playback bar with your best on that route in three things, which flight holds each, and where the flight you’re looking at ranks (“this flight: 2nd fastest of 3”). Each record counts only the flights it can judge — for example, only flights with a landing report count for the smoothest landing — so the totals can differ from row to row and from the number of flights on the route; hover the rank to see which flights count. A record held by the flight you’re looking at is marked with a 🏆. Click another flight’s record to compare with it (see Comparing Two Flights); the same flights carry a 🏆 in the Compare list too. Click the panel’s title to fold it away; FlightLog Analyzer remembers.

Your personal bests on a route, who holds each, and where this flight ranks.
• Best time — the shortest flight time. Only completed trips count: the flight must have landed at least once and lasted at least a minute, so an aborted start or a quick test doesn’t take the record. This one works for every flight in your logbook.
• Smoothest landing — the lowest sink rate on the landing that ended the flight (a touch-and-go earlier in the flight, or a bounce, doesn’t count). Gear-up landings don’t count, however gentle.
• Most stable approach — the approach to that final landing: stabilized by 1,000 ft beats stabilized by 500 ft, and between two equally stable approaches the smoother landing wins. An approach that wasn’t stabilized never holds this record.
The landing and approach records come from landing reports (see Landing Reports), which exist only for flights flown with FlightLog Analyzer 3.4.2.0 or later running. On a route you flew before that, those two rows say there are no landing reports or no stabilized approach yet, and fill in as you fly it again.
Every landing you make with FlightLog Analyzer running is measured the moment the wheels touch: how hard you came down, how many G it took, how you were pitched and banked, and exactly where on the runway you put it. Mission Debrief marks each touchdown on the map — click a marker for the full landing report.

Touchdown markers in Mission Debrief, colored by how firm each landing was (a red ring marks a bounce), with one landing’s report open.
• Filled dot — a landing, colored by its sink rate: green for smooth (under 240 fpm), yellow-green for normal (under 400), orange for firm (under 600) and red for hard.
• Red-ringed dot — a bounce: the aircraft went back into the air for at least a second before touching down again. It’s filled with its own sink-rate color and belongs to the landing just before it.
• Red dot — a gear-up landing, however gently it was made.
• Hover a marker for a one-line summary; click it for the full report.

A landing report: 271 fpm onto runway 24R at Crystal (KMIC), 954 ft past the threshold, 5 ft left of the centerline, with one bounce — after an approach that was anything but stabilized.
• Sink rate — how fast you were descending at the moment of contact, in feet per minute, with a rating: Very smooth (under 120 fpm), Smooth (under 240), Normal (under 400), Firm (under 600), Hard (under 800) and Very hard. MSFS measures it at the instant of touchdown, so it’s exact rather than read off a once-a-second sample.
• Peak G — the highest G-load in the three seconds after contact.
• Attitude and speed — bank and pitch at touchdown (pitch is positive nose-up), and your indicated airspeed and ground speed.
• Runway — the airport and runway you landed on, how far past the landing threshold you touched down (displaced thresholds included), how far left or right of the centerline, and how much runway was left ahead of you.
• Wind — the wind the sim had as you touched down, from the nearest recorded moment, in degrees true and knots, and what it meant on that runway: the crosswind and which side it came from, and the headwind or tailwind. A tailwind, or a crosswind of 15 kt or more, is shown in red. Flights recorded before FlightLog Analyzer 3.4.5.0 have no wind recorded, so their reports leave this out.
• Bounces — “Bounced once before staying down” (or more times).
• Gear-up landing — flagged in red when the aircraft has retractable gear and the gear handle was up.

A landing report with the wind at touchdown: 6 kt from 110° true on runway 24R at Los Angeles (KLAX), a 5 kt tailwind and 3 kt from the left, shown in red because of the tailwind.
Practicing landings? Each landing report ends with a link, Compare with my other landings on 24R → (for whichever runway it was). Click it for a table of every landing you have recorded on that runway — from this flight and from any other flight that started or ended at that airport, touch-and-goes included (a bounce belongs to the landing before it, so it isn’t a row of its own) — oldest first, with the one you came from highlighted.

Nine landings on Crystal’s runway 32 from three flights, side by side: the best in each column is marked, and the line underneath compares your latest landings with your earliest.
• Sink rate — with its rating, as in the landing report. A gear-up landing shows as such.
• Peak G — the highest G in the three seconds after contact.
• Touchdown — how far past the threshold you touched down. The best is the one closest to the standard aiming point, 1,000 ft past the threshold, not simply the shortest.
• Off centerline — how far left (L) or right (R) of the centerline.
• Approach stabilized — by 1,000 ft, by 500 ft, or not stabilized (blank when the approach was flown too low to judge).
A 🏆 marks the best value in each column. Gear-up landings, and landings MSFS didn’t report (“about … fpm”), never take a best. Once there are at least four landings to go on, the line under the table compares the average sink rate of your latest landings with your earliest ones (“Your last 5 landings averaged 210 fpm; your first 5 landings averaged 380 fpm”), so you can see whether practice is paying off.
Click a landing from the flight you’re debriefing to jump playback to it; click one from another flight of the same route to compare that flight with this one (see Comparing Two Flights). The ✕ closes the table. Like landing reports themselves, the table only includes flights flown with FlightLog Analyzer 3.4.2.0 or later running.
Below the touchdown numbers, the report judges the approach that led to it, the way airlines do: by 1,000 ft above the runway (500 ft at the latest, and for a visual pattern) the aircraft should be “stabilized” — descending gently, at a steady speed, lined up with the runway and on a normal glide path. Heights are measured above the spot where you touched down, from the flight’s recorded telemetry.

The Approach section of a landing report: the verdict, then the numbers at 1,000 ft and 500 ft.
• Stabilized by 1,000 ft ✓ — (green) everything was within limits from 1,000 ft down.
• Stabilized by 500 ft ✓ — (green) for a pattern flown entirely below 1,000 ft, where 500 ft is the height that applies.
• Stabilized by 500 ft, not by 1,000 ft — (amber) it settled down, but late.
• Not stabilized at 500 ft — (red) still outside the limits at 500 ft. In real life that’s a go-around.
• Too low to judge — the approach was flown below 500 ft the whole way.
Under the verdict is a line for each height the approach came down through — how far out you were, then the four checks. Any number outside its limit is shown in red:
• Sink — the fastest descent from that height down to 100 ft; no more than 1,000 fpm.
• Speed — how much your true airspeed varied from that height down to 200 ft; no more than 15 kt. The recording has no indicated airspeed or approach speed to compare with, so it judges how steady the speed was, not whether it was the right one.
• Lined up — the angle off the extended runway centerline, seen from the threshold; within 2.5° left or right.
• Glide path — the angle down to a point 1,000 ft past the threshold; between 2° and 4° (3° is standard).
Bounces aren’t judged separately — they belong to the landing before them. Each landing is judged only from the 15 minutes before it, and never from before the previous touchdown, so every circuit of a touch-and-go session gets its own verdict.
• Touchdowns are recorded live, along with the rest of the telemetry, while FlightLog Analyzer is running during the flight — so flights flown before version 3.4.2.0, or with the program closed, have no landing reports. Like telemetry, this needs a PRO license once the trial period ends.
• A touch-and-go counts as a landing. A second touchdown within 20 seconds on the same runway counts as a bounce of the landing before it.
• For a gear-up landing MSFS doesn’t report the moment of contact, so its numbers come from the instant just before it, and the sink rate reads “about”.
• The runway comes from FlightLog Analyzer’s own airport data. If you touch down off a runway, or on one that isn’t in that data, the report says so and leaves out the runway lines. The data and the sim’s scenery can differ by a few feet, so treat small centerline offsets as approximate.
Choose Profile: Route (Vertical) in a Mission Debrief and the strip shows your whole flight against its flight plan and the terrain, just as the ATC View does live — but because the flight is over, the summary line turns from a countdown into a report card: how far you planned to fly versus how far you actually flew, where you really started down compared with the plan, and the farthest you strayed from the route.

A finished Phoenix–Las Vegas flight at 12,500 ft: the descent began 51.5 nm out instead of the 3° plan’s 32.4 nm, and the aircraft strayed up to 3.7 nm from the route, 327.0 nm into the flight.
|
What you see |
What it means |
|
ROUTE 977.5 nm |
Length of the planned route, departure to destination through every waypoint. |
|
FLOWN 975.1 nm |
Distance actually flown along the recorded track. More than ROUTE means extra miles — vectors, holds, sightseeing; a little less usually means you cut a corner, or telemetry started after takeoff. |
|
CRUISE 12,500 ft |
The plan’s cruise altitude (PEAK when the route was too short to reach it). |
|
DESCENT BEGAN 51.5 nm out (3° plan: 32.4 nm) |
Where you actually left cruise altitude, compared with the 3° Top of Descent. Earlier than the plan means a longer, shallower descent; later means you had to come down steeper than 3°. |
|
(cruise altitude never reached) |
You never got within 100 ft of the planned cruise altitude, so there is no level-off or descent point to compare. |
|
MAX OFF ROUTE 3.7 nm (at 327.0 nm) |
The farthest you were to the side of the planned route at any point in the flight, and how far along the route that happened. Reads STAYED ON ROUTE if you were never more than half a mile off. |
|
SAFE ALT 12,400 ft |
The route’s highest leg safe altitude, from the terrain along the route — the same check the ATC View and Flight Planner make. |
Take the Phoenix–Las Vegas flight in the picture above:
• ROUTE 977.5 nm vs. FLOWN 975.1 nm — almost identical, so overall the flight followed its plan closely.
• DESCENT BEGAN 51.5 nm out (3° plan: 32.4 nm) — the pilot started down about 19 nm early. Losing the same 10,319 ft over 51.5 nm instead of 32.4 nm works out to about 200 ft per nm — roughly a 2° descent instead of 3°. Nothing wrong with that, but it means more time spent at lower, less efficient altitudes. Next time, waiting for the TOD marker would save several minutes of low-level cruising.
• MAX OFF ROUTE 3.7 nm (at 327.0 nm) — hover the profile around 327 nm and the green dot on the map shows exactly where the aircraft wandered off, and the readout shows how far off route each point was.
• SAFE ALT 12,400 ft with a 12,500 ft cruise — the plan cleared the terrain, and the solid brown terrain flown over confirms the ground the aircraft actually passed over.
And a short VFR example from a real flight — Prescott (KPRC) to Cottonwood (P52) with a sightseeing detour north past Clarkdale:
ROUTE 19.5 nm FLOWN 24.6 nm MAX OFF ROUTE 6.0 nm (at 15.1 nm)
The flight covered 5.1 nm more than the direct route — that is the detour — and at its widest the track was 6.0 nm from the planned line, 15.1 nm along the route. The maximum always covers the whole flight, right up to the destination, so it always matches what hovering that point shows.
The route profile places everything by how far along your flight plan it is, so it can only draw the part of the flight that moves forward along the route. Anything you fly after that — circling past the destination, sightseeing on the way home, flying back to where you started — appears in its own section on the right of the strip, past a dashed divider labeled AFTER ROUTE with the distance flown there. That section is laid out by distance flown rather than along the route, with the altitude you flew and the ground beneath you, so hovering the far right of the strip always takes you to the very end of the flight.
Example — A flight left Los Angeles (KLAX) on a 24.5 nm plan to a destination near El Monte, then circled over the San Gabriel foothills and flew back west toward Malibu, 101.5 nm in all. The summary reads:
ROUTE 24.5 nm FLOWN 101.5 nm MAX OFF ROUTE 2.4 nm (at 22.1 nm)
AFTER ROUTE 74.2 nm
The first 24.5 nm are drawn along the route; the other 74.2 nm are drawn after the divider. Hover just past the divider and the readout says after route +0.7 nm, with your altitude and the ground height at that point, while the green dot on the map shows where that was.

Hovering just past the AFTER ROUTE divider: 0.7 nm after leaving the route, at 1,555 ft over ground at 397 ft — the green dot on the map marks the spot.
MAX OFF ROUTE only counts the part of the flight drawn along the route — what you fly after leaving it isn't a deviation from it. The line along the route also only ever moves forward: if you briefly turn back over part of the route, in a hold or a turn in the pattern, the line steps over it instead of drawing back over itself, and hovering moves the green dot forward through the flight as you move right. The AFTER ROUTE section appears only in Mission Debrief, and only when there is at least 1 nm of flying after the route; in the ATC View the profile is about what is still ahead of you.
FlightLog Analyzer began saving each flight plan’s cruise altitude and departure airport with version 3.4.0.0, so flights recorded with earlier versions don’t have them. For those flights the Mission Debrief still shows everything else: the route from the logbook’s departure airport through the recorded waypoints to the destination, the altitude you flew, the terrain and safe altitudes along the route, FLOWN versus ROUTE, and MAX OFF ROUTE. There is simply no amber planned line, and the summary notes “(no planned cruise altitude available)”.

A flight recorded before version 3.4.0.0: no planned line, but the route, flown altitude, terrain, safe altitudes and off-route summary are all there.
A debrief is a finished recording, so the profile never says it is “waiting” for anything. A flight flown without a flight plan — or with a plan that starts and ends at the same airport, like a pattern flight — still gets a profile: the whole flight by distance flown, with “(no flight plan was recorded: whole flight shown)”. The same happens when the recorded plan clearly belongs to another flight (“this flight never came within 836 nm of the plan: whole flight shown”); its route, destination and waypoints are then hidden from the map too. If anything else is missing, it is missing for good, and the message says what the recording lacks:
|
Message |
What it means |
|
Route profile: this flight has no recorded positions to start the route from -- try Profile: MSL Alt |
A plan was recorded, but there are no telemetry positions and no departure airport FlightLog Analyzer recognizes to start the route from. |
By default, you can open multiple Mission Debrief windows side by side. To restrict this to a single open debrief at a time, enable Allow Only 1 Open Mission Debrief in the User Preferences.
Aside from the full-featured Mission Debrief, FlightLog Analyzer offers two lighter-weight visualizations for any flight in your logbook: the Flight Map and the Flight Profile. Both are reached by right-clicking a flight on the main display (or on the Group Analysis display) and selecting from the context menu:
• Flight Map — the path across the ground
• Flight Profile — altitude (and optionally speed) vs. time or distance
• Export the selected flight(s)
• Delete the selected flight(s) with the Logbook Cleaner
|
Note: To see "Google Earth" as a Flight Map option in the context menu, Google Earth Pro must be installed. If you don't want to install it, you can still export flights as KML and import them into the web-based version of Google Earth. |
Right-click → Flight Map opens the path of the flight on a map of the Earth. You can use the built-in viewer, or — if Google Earth Pro is installed — view it in 3D in Google Earth. Multiple flights can be selected and displayed on the same map in either viewer.
The menu in the upper-right corner of the map offers these display options:
• Satellite Overlay — turns on satellite imagery. Deselect for a standard street view.
• Basic Flight Path — draws a red line directly connecting origin to destination (great-circle).
• Raw Flight Path — draws a black line through the original sparse points logged by Flight Simulator, with no smoothing applied.
• Smoothed Flight Path — draws a green line representing FlightLog Analyzer's best guess at the actual path between the sparse logbook points.
• Telemetry Flight Path — draws a blue line tracing the true high-resolution path. Only available when telemetry was captured and is currently enabled for the flight.
• Origin / Destination — toggles the green and purple markers at the start and end points of the flight.
The contrast between the raw logbook path and the telemetry path is striking. The raw logbook stores only a handful of points — sometimes as few as six for a multi-hour flight — and the smoothing algorithm does its best to interpolate between them. Telemetry, by comparison, records once per second and produces a path that matches the actual flight exactly.

Raw and Smoothed paths in the Built-in Viewer

Telemetry path in the Built-in Viewer
When Google Earth Pro is installed, you can view the flight path in full 3D — pan, rotate, and zoom to examine it from any angle. The layer panel on the left of Google Earth, under Temporary Places → FlightLog Analyzer, contains:
• Start and End Markers — toggle the origin/destination markers.
• Detailed Routes — green line showing the smoothed path (or the true telemetry path, when telemetry is enabled).
• Raw Routes — red line showing the original Flight Simulator path with no smoothing.
Default settings for which layers to include can be configured in the User Preferences.

Flight path in Google Earth Pro
Right-click → Flight Profile opens the altitude profile of the flight. Use the Time / Distance buttons at the top to toggle between altitude vs. time and altitude vs. distance flown.

Flight Profile — altitude vs. time

Flight Profile — altitude vs. distance
The chart can display up to three altitude curves and a speed curve:
• MSL — altitude above mean sea level, in feet.
• AGL — altitude above ground level, in feet.
• Ground Elevation — the terrain elevation under the aircraft, calculated as MSL minus AGL.
• Speed — true airspeed in knots. Only available when telemetry was captured for the flight.
The Ground Elevation curve is optional and can be toggled in the User Preferences.
The Flight Filtering feature limits the flights shown on the main display to those matching one or more criteria — say, all flights originating from a particular airport, all flights in a specific aircraft model, all flights flown in IFR conditions, or any combination of these.
Filtering affects more than just the table: the Charts and Graphs panel updates to summarize only the filtered flights.
1. Click the icon in the left corner of the filter panel to expand it. A selection box appears for each filterable column.

Filter panel collapsed and expanded
2. Click the cyan down-arrow on a filter to open its dropdown. The dropdown lists every value present in that column.
3. Check the values you want to keep. The selection control is shaded green to show that criteria are queued, but filtering is not yet active.
4. Click the Activate Filters button to apply your selections. The main display and the charts update to include only matching flights.
5. Add more filters as needed. Multiple filters combine with AND logic — a flight must match every active filter to be included.
6. Click Deactivate Filters to temporarily turn filtering off without clearing your selections; click Activate Filters again to re-apply. Click Reset Filters to clear all selections and start fresh.
Instead of opening a filter's dropdown and checking boxes, you can type directly into the filter's text box and press Return. Whatever values match your typed text are selected and the filter is applied immediately.
For example, typing
ksez into the Origination Airport filter and pressing Return adds KSEZ to the active filter and refreshes the display.
You can type into multiple filters in succession — each Return applies that filter on top of any others already active.
The text-entry feature also accepts partial strings. Type
ILS into the Planned Approach filter and press Return to display every ILS approach in your logbook, regardless of runway number.
If the dropdown is open while you type, the list of options narrows dynamically with each character.
Every filter has a checkbox to the left of its text box. By default, this checkbox is checked, meaning "include only the selected values." Uncheck it to invert the filter: the display will exclude the selected values instead.
For example, under the Flight Simulator Version filter, selecting 2020 with the checkbox
checked shows only FS2020 flights. Selecting 2020 with the checkbox unchecked shows everything except FS2020 flights.
The Reset Filters button clears every filter, but if you want to clear just one, triple-click its text box. (Double-click works too, but if the filter is currently active — shaded green — you'll need the third click.) The selection clears and the filter returns to its "show everything" default.
The two date boxes at the right end of the filter panel's top row, Flights From Date and Flights To Date, limit the list to a period. Tick a box to use it, pick the date, then click Activate Filters. Use just one for an open-ended range (everything since 1 January, or everything up to last summer), or both for a span, which can cross years. Both dates are included. A flight counts on the day it shows in the grid, following the GMT/Local setting, the same as the Activity Calendar. Combine them with the other filters, an aircraft model and a year for example, and the Charts & Graphs panel and the Airport Heat Map show just those flights. Reset Filters unticks both boxes.

The filter panel's new date boxes, Flights From Date and Flights To Date, at the right end of the top row.
Which aircraft do you really fly the most? Where did all those hours go last month? Group Analysis answers questions like these in one click, slicing your whole logbook by aircraft, airport, month or any other column and totaling each group.
Group Flights By categorizes and summarizes your flights by any flight attribute. A handful of common groupings include:
• 30, 45, 60, or 90 day summaries
• Aircraft type, model, or manufacturer
• Weather conditions
• Flight Simulator version (2020 or 2024)
• Flight type (Discovery, Free Flight, Tutorial Missions, Landing Challenges, etc.)
• Flight end status (Success, Crash, Unsuccessful Mission, Incomplete, etc.)
The Limit to Last selection further restricts the results to flights occurring within the last N days.
Group Analysis opens in the Bars view, which ranks every group as a horizontal bar so the biggest ones stand out at a glance. Use the Bars | Table switch at the top of the window to move between the Bars view and the classic Table view; the window remembers which one you last used.

Group Analysis in the Bars view, grouped by aircraft class and sorted by average flight time
• Summary cards across the top show the totals for everything on screen: flights, flight time (with the day/night split), distance, and takeoffs/landings.
• The Bars show list chooses what the bars measure. Every column of the Table view is available: Flights, Flight Time, Day and Night Flight Time, Distance, TakeOffs, Landings, the Day and Night TakeOffs and Landings (when those columns are enabled), and the average Time and Distance per flight.
• The Day / Night strip at the right of each row shows how much of that group’s time, takeoffs, or landings happened in daylight (blue) versus after dark (purple). It is left out when the bars already show a day-only or night-only measure.
• Hover over a row to see every value for that group at once.
• Click the name header or the measure header to sort by it; click again to reverse the order. The 30, 45, 60, and 90 day, 6 month, and 1 year summaries sort by how long a period they cover.
• Click a row to select it; Ctrl-click or Shift-click selects several, and the arrow keys move through the list. Double-click a row, or right-click it, for the same options as the Table view.
Choose Table to see every column at once in the classic grid:

Group Analysis in the Table view, grouped by aircraft manufacturer and sorted by flights
All the right-click options from the main display are also available here — Flight Map, Flight Profile, Export, and Delete via Logbook Cleaner.
Exporting the totals to Excel — Click Export CSV... (at the right end of the row above the grid, in either view) to save the group totals as a .csv file that opens straight in Excel: one row per group, with every column the Table view shows, in the same order and sort, followed by the totals row. Grouped by aircraft type or model, for example, that’s your total flight time, flights and distance for each plane. Values are written the way they appear on screen (flight times as hh:mm:ss). Like the other exports, this needs a registered license.
Each row on the Group Analysis window represents a collection of individual flights. To see those flights, right-click a row and select Group Details (or simply double-click the row).
The main display will be filtered to show only the flights in that group. You can double-click another row to see its flights, or close the Group Analysis window to return to the full unfiltered logbook.
In this example, a user has flown ILS and RNAV approaches. The RNAV row shows seven flights; double-clicking it filters the main display to those seven flights so they can be examined individually.
The exporter can write your logbook out in a variety of formats, for use in other flight-tracking applications or just for safe-keeping. Open it from File → Export…

Export dialog
Choose the file type that matches your destination application:
• .CSV — one flight per line, attributes separated by commas. Universally readable.
• .XML — structured format suitable for cross-application data exchange.
• .KML — for mapping applications, including Google Earth and Google Maps.
• LNM — CSV variant for Little Navmap. See Troubleshooting for import notes.
• Volanta — CSV for the Volanta application. See Troubleshooting.
• SKTP — CSV for SimToolKitPro. See Troubleshooting.
• Sky Dolly — GPX format, one file per flight. See Troubleshooting.
• Basic Flight Info — flight attributes only (date, airports, aircraft, times, etc.). Does not include the GPS track.
• Basic + Flight Route — everything in Basic Flight Info plus the GPS coordinates of the flight path.
• Only the grid’s columns, in the grid’s order — a checkbox for the .CSV format. Tick it and the file holds just the columns you’ve left showing in the main grid, in the order you’ve dragged them to, with each value written the way the grid shows it (dates follow the UTC/Local and 24h/12h switches), ready for Excel or Google Sheets. To choose the columns, hide or move them in the grid first. While it’s ticked, Basic Flight Info and Basic + Flight Route don’t apply, since the grid has no flight route. Leave it unticked for the full CSV, with every column in its usual order. FlightLog Analyzer remembers your choice.
To export a subset of flights, enter their numbers in the Flight Number(s) to Export field. Use commas to separate individual numbers and dashes for ranges (for example,
3-7, 12, 15-20). Leave the field blank to export every flight.
General preferences for FlightLog Analyzer live under Edit → Preferences… Each option is described briefly below.

User Preferences dialog
• Auto-Launch ATC View — opens the real-time moving map automatically when a flight starts in the sim. If disabled, you can still open the map manually with F6 or via View → ATC View – Real-Time Flight Map.
• Show Basic Flight Paths — toggles the straight-line connection between flight start and end on the Flight Map.
• Show Raw Flight Paths — controls whether the raw (un-smoothed) Flight Simulator path is included when exporting to Google Earth. Has no effect on the Built-in Viewer, which always shows both.
• Smooth Altitude Profiles — applies smoothing to altitude curves to soften the abrupt jumps that result from Flight Simulator's sparse GPS logging.
• Night Takeoffs and Landings From — when a takeoff or landing counts as a night one: the end of civil twilight (the default, as the FAA, ICAO and EASA log them), one hour after sunset (FAA night currency), or sunset. Night flight time always starts at the end of civil twilight. See Day and Night in Your Logbook.
• Use Larger Font — increases the font size on the main and Group Analysis grids.
• Minimize to the Tray — minimizing puts FlightLog Analyzer next to the clock instead of on the taskbar. Off unless you tick it; see Running Next to the Clock.
• Highlight Slewing Flights — yellow row highlight for flights that used slew mode.
• Highlight "In Vicinity" Flights — blue cell highlight when Flight Simulator records a flight as landing "in the vicinity of" an airport rather than at it.
• Use Satellite Overlay — default to satellite view (vs. street view) on the Flight Map.
• Allow Only 1 Open Built-In Map Viewer — when set, opening a new Flight Map closes any previously open one. Affects the Built-in Viewer only, not KML viewers.
• Allow Only 1 Open Mission Debrief — when set, opening a new Mission Debrief closes any previously open one.
• Auto-Open Mission Debrief After Flight — opens a recorded flight’s Mission Debrief by itself when the flight ends. On unless you untick it; see When a Flight Ends.
• Launch with Microsoft Flight Simulator — Flight Simulator launches FlightLog Analyzer every time you launch it, so every flight is recorded. Shows what Flight Simulator’s list says right now, and changes it right away; see Launch with Microsoft Flight Simulator.
• Allow Only 1 Open 'Profile Viewer' — same idea for Flight Profile windows.
• Show Calculated Elevation — draws the ground elevation curve on the Flight Profile.
• Flattened Altitude — pins the altitude line to the ground on Flight Maps (effectively hides altitude).
• Extrude Altitude — draws a vertical "curtain" between the altitude line and the ground.
• Short Flight Duration — defines the time threshold below which a flight is considered "undesirably short" by the Logbook Cleaner's auto-select feature.
• Short Flight Distance — same idea for distance.
• Steam Options — your Steam ID for the Achievements Tracker. Only enabled when you have one MS Store install and one Steam install loaded simultaneously.
• Waypoints — ATC View — controls which categories of navigation fixes appear on the real-time ATC View map: Traffic Pattern (airport approach/departure waypoints from the active flight plan), Intersections (named airway and RNAV fixes), VORs, and NDBs. Each can be toggled independently.
• Waypoints — Mission Debrief — same four toggles for the Mission Debrief replay map. Settings are independent of the ATC View, so the categories you display while flying don't have to match what's shown during playback.
The Logbook Cleaner permanently removes unwanted flights from Flight Simulator's logbook. It's a PRO-license tool, available from Edit → Delete Unwanted Flights…
|
Important: This tool literally modifies Flight Simulator's logbook file. Although a backup is made automatically before every edit, making your own backup for safe-keeping is wise — use Edit → Backup the FS Logbook. |
|
Important: When you press the SNIP! button, the listed flights are stripped from the logbook permanently. The next time you start Flight Simulator, those flights will no longer exist. They can be restored only by restoring an earlier logbook backup. Telemetry data for deleted flights is also permanently lost and will not be restored by reverting to a logbook backup. |
|
Important: Do NOT use this tool while Flight Simulator is running — the logbook is being rewritten. |
You have three options for selecting flights for deletion:
1. Manual flight number entry
Type flight numbers directly into the input box. Flight numbers begin at 1 (not 0), so 1 is the first flight in the logbook. Separate individual numbers with commas, or use the shorthand
start-end for ranges. For example, 3-7 is equivalent to 3, 4, 5, 6, 7.
2. Auto-select by attribute
• Short Duration Flights — selects every flight shorter than N minutes (N comes from User Preferences).
• Short Distance Flights — selects every flight shorter than N nautical miles.
• Crashed Flights — selects every flight that ended in a crash according to Flight Simulator.
3. Select from the main display
Highlight the rows you want to delete on the main display (Shift/Ctrl for multi-select), right-click, and choose Delete Flight(s) from the popup menu. The Logbook Cleaner opens pre-populated with those flight numbers.
If multiple methods are used at once, the combined set of flight numbers is generated.
When you're ready, press SNIP! — a backup is made automatically, and a confirmation dialog tells you how many flights are about to be deleted before any change is applied.

Logbook Cleaner dialog
Every Logbook Cleaner operation creates a restore point. To revert, use Edit → Restore FlightLog… Each restore point shows the date, time, and filename of the saved logbook.
Select the version you want and click Restore. The master logbook file is overwritten with the version you chose.
To delete restore points you no longer need, select them and press the Delete key — the records are removed from the display. Press Proceed to actually move the backup files to the Recycle Bin.
|
Important: Just as with the Logbook Cleaner, do not use the Restore tool while Flight Simulator is running. |

Checkpoint Restore tool
Checkpoint Restore tool
The Flight Fixer corrects flights with missing takeoffs and/or landings — those frustrating logbook entries where Flight Simulator records the flight but logs zero takeoffs or landings. This is a PRO-license tool, available from Edit → Fix Missing Takeoffs and Landings…
A missing takeoff can be restored if the flight:
• Did not start "in vicinity" of an airport — it must start at an airport.
• Started on the runway, at a gate, or on the ramp.
• Did not end in a crash (it may have crashed at takeoff).
• Is a Free Flight (the only flight type eligible for correction).
A missing landing can be restored if the flight:
• Was actually airborne before landing.
• Did not end in a crash.
• Did not end "in vicinity" of an airport — it must end at an airport.
• Is a Free Flight.
Flights eligible for correction are marked in red on the main data table.
|
Important: Like the Logbook Cleaner, the Flight Fixer literally modifies Flight Simulator's logbook. Automatic backups are made before every edit, and you can also make manual backups via Edit → Backup the FS Logbook. |
|
Important: Do NOT use this tool while Flight Simulator is running. |
Three options, parallel to the Logbook Cleaner:
1. Manual flight number entry
Same syntax as the Logbook Cleaner — comma-separated numbers and dash-separated ranges.
2. Auto-select
• Missing Takeoffs — selects every flight that's missing a takeoff.
• Missing Landings — selects every flight that's missing a landing.
3. Select from the main display
Highlight the rows on the main display, right-click, and choose Fix Flight(s). The Flight Fixer opens pre-populated with those flight numbers.
When you're ready, press Fix It! — an automatic backup is made and a confirmation dialog appears before any changes are applied.
Flight Fixer uses the same restore-point system as the Logbook Cleaner. To roll back changes, open Edit → Restore FlightLog… and select the appropriate restore point.
Ever struggled to complete a Flight Simulator achievement, baffled about which services or aircraft you're still missing? The Achievements Progress Tracker is built for exactly that.

The Flight Achievements window: each achievement, its status, progress toward it, and what it takes
It pulls your achievement status directly from your Microsoft / Xbox account in real time, displays your progress without making you launch the sim, and — where possible — provides guidance on what activities remain to complete each achievement.
Because the Tracker queries your Microsoft / Xbox account, an active internet connection is required, and you must sign in. The first time you open the Tracker, your web browser will be redirected to the Microsoft / Xbox login page. After a successful login, control returns to FlightLog Analyzer and your achievements populate.
Login tokens are typically good for 12+ hours. While they're valid, the Achievements page opens immediately without requiring another login.
|
Note: FlightLog Analyzer reads only achievement statistics — no other personal information is accessed. |
Achievements work somewhat differently on Steam than on the Microsoft Store version. The Microsoft Store implicitly tracks "percent complete" for each achievement; Steam does not. FlightLog Analyzer reconstructs those values for Steam users, but because Asobo doesn't publish their exact calculation, results may differ slightly from what you see in the sim.
To use the Achievements Tracker with a Steam installation:
1. Enter your Steam ID in the Preferences menu (the field is only enabled when both Steam and MS Store installations are detected).
2. Set your Steam profile's My Profile (or at least Game Details) to Public.
If the Tracker tries to access your achievements while your permissions are still private, FlightLog Analyzer will automatically open the Steam privacy settings page for you. Manual steps:
1. On the Steam website or app, click your nickname (upper-right) and choose View my Profile.
2. Click Edit Profile.
3. Go to the Privacy Settings tab.
4. Set My Profile (or at least Game Details) to Public.
|
Note: No private, confidential, or sensitive information is disclosed by setting Game Details to public. |
FS2024 achievements are not yet supported.
For more on Flight Simulator achievements:
• flight.wiki.gg — MSFS 2020 Achievements
• gamepressure.com — MSFS Achievements list
Flight Simulator records aircraft model names with all sorts of trailing detail — N-numbers, livery colors, variant codes, and other quantifiers that don't really matter when you're trying to summarize "how much King Air time have I logged?" The Aircraft-Model Name Translation feature lets you collapse all those variants into a clean, canonical name.
Translations affect only what FlightLog Analyzer displays — your Flight Simulator logbook is not modified.
Say your logbook contains flights in multiple variants of a Beech King Air 350 and a Beech V35B Bonanza. By default, the Group Analysis would split them across many rows. To consolidate them all under a single name, edit the translations file via Edit → Edit Aircraft Model Translations (or press F10).
The file uses CSV format with two required columns and two optional additional columns:
• Column 1 — the Aircraft Model substring to match against.
• Column 2 — the replacement Aircraft Model name.
• Column 3 (optional) — the replacement Manufacturer name.
• Column 4 (optional) — a value for the grid’s Class column.
Column 4 lets you also set a value for the grid’s Class column. For example:
"737", "737-800", "Boeing", "Airliner"
—sets the Class to “Airliner” for any model containing “737”.
By default this column is labeled “Class” in the grid. To rename it — for example to “Passenger/Cargo” — add a line anywhere in the file starting with “!”, like this:
!Passenger/Cargo
To consolidate every V35B Bonanza variant under one name, add this line:
"Beechcraft V35B Bonanza", "Beechcraft V35B Bonanza"
This tells FlightLog Analyzer that any model name containing "Beechcraft V35B Bonanza" should be replaced with "Beechcraft V35B Bonanza" — effectively trimming any trailing variant detail.
You can also rewrite the name entirely. For example:
"Beechcraft V35B Bonanza", "Red Rubber Ducky"
…would make every V35B Bonanza show up in the display as "Red Rubber Ducky."
To both rename a model and replace its manufacturer:
"Beechcraft King Air 350", "King Air 350", "Beech"
Press F5 to refresh, and every King Air 350 variant displays with the model "King Air 350" and the manufacturer "Beech."
An asterisk (*) matches any sequence of characters — a Joker, in poker terms. For example:
"Beech*350*", "Beechcraft King Air 350"
…matches any model name that contains "Beech" followed somewhere by "350." This is convenient but powerful, so be careful — that pattern would also match "Beech Comber Classic N1350B" and rewrite it as "Beechcraft King Air 350," which probably isn't what you want. Tighten your pattern when ambiguity is a risk.
If you're comfortable with regular expressions, FlightLog Analyzer accepts them directly. A full RegEx tutorial is beyond the scope of this guide, but here are two illustrative examples.
Removing color from "Pilatus PC-6 Red N222A" while keeping the tail number:
"Pilatus PC-6 (*) (*)", "Pilatus PC-6 $2"
The parenthesized groups are numbered left to right — $1 is the first, $2 is the second. The substitution string keeps "Pilatus PC-6" and appends only $2 (the tail number), discarding $1 (the color).
Collapsing every PA-24 Comanche variant in the 200hp range under a single name:
"(*) (PA-24)-(2[0-9]{2} Comanche) (*)", "PA-24 (200 Series)"
This pattern matches "anything PA-24-2xx Comanche anything" regardless of manufacturer or trailing detail, and rewrites all of them to "PA-24 (200 Series)." A parallel entry can be added for the 300 Series:
"(*) (PA-24)-(3[0-9]{2} Comanche) (*)", "PA-24 (300 Series)"
• Lines beginning with # are comments and are ignored by the parser.
• Standard RegEx uses .* for "any characters." FlightLog Analyzer also accepts a bare * as shorthand to keep your translation file more readable.
• Trailing items on a translation line are treated as comments — you can add reminders to yourself:
"Pilatus PC-6 (*) (*)", "Pilatus PC-6 $2", "removes color, keeps tail"
Every time a new or modified FS2020 or FS2024 logbook is loaded, FlightLog Analyzer archives a copy automatically. This is essential protection: when you eventually uninstall FS2020, the original FS2020 logbook is deleted along with it. The archived copy lets FlightLog Analyzer keep showing your historical FS2020 flights as part of the consolidated view.
Archived logbooks are stored at: %localappdata%\FlightLogAnalyzer\FS2020 Archive
After uninstalling FS2020, choose the archived file when assigning the FS2020 logbook via File → Choose Logbook File(s).
You can back up Flight Simulator's logbook at any time, for any reason. Use Edit → Backup FlightLog… One creative use: keep a separate logbook for each aircraft type, restoring the appropriate one before a session — useful for keeping helicopter time, GA time, and airliner time cleanly separated.

Manual backup dialog
Hot keys speed up common actions, especially useful when you're mid-animation or deep in the data table and don't want to leave for the menu. The most commonly used hot keys are listed below — press F1 in any window (or choose View > Keyboard Shortcuts) for the complete list, grouped by the window each works in.
|
F1 |
Open the Keyboard Shortcuts window: every hot key, grouped by window |
|
F2 |
Open the User Guide from FlightLogAnalyzer.com |
|
F3 |
Close the active window (or Snap to Overlay Zoom in the ATC View, Mission Debrief and Flight Planner) |
|
F4 |
Open the Preferences form (or toggle Auto-Center in ATC/Debrief windows) |
|
F5 |
Refresh the main display, re-reading the logbook and AircraftModelTranslation.txt (or Zoom-to-Flight in ATC/Debrief) |
|
F6 |
Toggle destination lines on the ATC/Debrief map (or open the ATC View) |
|
Shift+F6 |
Open the Flight Alerts window |
|
F7 |
Open the Logbook Exporter (or the Nearest Airports list in the ATC View) |
|
F8 |
Open the Logbook Cleaner |
|
F9 |
Open the Flight Fixer |
|
F10 |
Open the Aircraft Model Translation file in Notepad |
|
Shift+F10 |
Open your own airport names (MyAirportNames.txt) in your text editor |
|
F11 |
Toggle Dark Mode |
|
F12 |
Open the Flight Planner |
|
Shift+F12 |
Open the Navigation Database |
|
Ctrl+F11 |
Toggle horizontal grid lines (Day / Night shading in the ATC View and Mission Debrief) |
|
Shift+F11 |
Toggle vertical grid lines |
|
Ctrl+F10 |
Open the color customization file |
|
Esc / Ctrl+W |
Close the active window or dialog (does not close the main form) |
|
Space |
Play / pause the flight in Mission Debrief |
|
M |
Measure distance and course on the ATC View / Debrief map |
A subset of FlightLog Analyzer's colors can be customized via a plain-text file. Open it with Edit → Edit App's Color Selections (Ctrl+F10), or directly at:
%LocalAppData%\FlightLogAnalyzer\Colors.txt
Change the named color values to whatever you like. Only the entries listed in the file are customizable.
For a complete list of valid C# color names, see flounder.com/csharp_color_table.htm.
The CLI lets you script common operations without opening the UI. The supported operations are creating backups of the FS202x logbooks, and performing exports.
To list the supported arguments, run with --help. The notation -m, --mode indicates that the short and long forms are equivalent.
The first usage example creates an export, behaving exactly as the in-UI exporter does. The example arguments produce a CSV export of flights 1–5, 8, and 10–15, with the current date substituted into the output path and the current time into the filename. The
--details flag tells the export to include the GPS path coordinates.
The second example creates a backup of the FS202x logbook. The same date/time substitutions are made, along with a {count} placeholder for the number of records in the backup.
This guide was contributed by user Gabriele Marrč Brunenghi.
There are several ways to run a Windows .exe on Linux. For simplicity, this walk-through uses Lutris.
Follow the official instructions at
1. Launch Lutris.
2. Click the + button in the upper-left corner.
3. Choose Install Windows game from an executable.
4. Name the app whatever you like; keep Windows 10/11 as the system.
5. Choose Wine Setup file Install → Continue.
6. Click the three-dots button and select the installer.exe you downloaded from FlightLogAnalyzer.com.
7. Click Install.
8. Follow the installation, leaving the defaults — but uncheck the "Launch" box at the end.
9. Close the installation window.
If you launch MSFS from Steam, the logbook path is buried and hidden by default. Creating a symlink to it makes navigation much easier.
1. In your file manager, enable Show Hidden Files (under View).
2. Pick an easy-to-find location for your link — Documents, for example.
3. Create a symbolic link to your logbook file using the method appropriate to your distro. In SteamOS: right-click → Create New → Link to File or Directory → browse to file → Link to File.
Typical paths:
/home/<user>/.steam/steam/userdata/<steam-id>/<game-id>/remote/kh_logbook
• user — your Linux username (default is "deck" on SteamOS).
• steam-id — usually the folder with the largest number. Verify by looking inside for the game-id folder.
• game-id — 1250410 for MSFS2020, 2537590 for MSFS2024.
1. Launch FlightLog Analyzer via Lutris.
2. Dismiss any errors that appear — Lutris can't auto-find the logbook.
3. Choose File → Manually Load Logbook.
4. In the file dialog, navigate to your symlink (the path begins at /home/<user>/, e.g. /home/deck/Documents on SteamOS).
5. Select the kh_logbook symlink. Done.
|
Note: Lutris can create a Steam entry for the app, allowing you to launch it in Big Picture or Game Mode, but some additional tweaking is required for it to display correctly. Currently not recommended. |
A suffix on an instrument approach name — such as the "Y" or "Z" in "ILS-28-Y" — indicates that more than one approach exists to the same runway using the same type of navigation aid. The suffixes distinguish between approaches that may have different procedures, minimums, or equipment requirements.
Key points:
• Multiple approaches — when two or more straight-in approaches exist to the same runway using the same guidance type (ILS, RNAV, etc.), a letter suffix differentiates them.
• Different procedures — each approach may have different entry procedures, missed approach procedures, or decision heights. One may require GPS, another may not.
• Different minimums — landing minimums (visibility, altitude) typically improve as the suffix moves up the alphabet: Z usually has the lowest minimums, then Y, then X.
These distinctions let pilots pick the appropriate approach for their aircraft's capabilities and the current conditions.
|
Note: Countries outside the US sometimes use letter designations other than X/Y/Z. |
Quick definitions for the terms used by the vertical profiles in the ATC View, Mission Debrief and the Flight Planner, and by Auto VOR Route and Auto Procedures. See the chapter Vertical Profiles Explained and the Flight Planner’s Auto VOR Route and Auto Procedures sections for the full explanations and worked examples.
|
Vertical profile |
A side view of a route: distance along the route left to right, altitude bottom to top. |
|
TOC |
Top of Climb — where the climb ends and level cruise begins. |
|
TOD |
Top of Descent — where the descent should begin to arrive at the destination on a 3° path. |
|
3° path |
The standard descent angle: about 318 ft per nautical mile, or 1,000 ft every 3 nm. To fly it, descend at about 5 × your ground speed in fpm. |
|
Climb gradient |
Feet gained per nautical mile flown. FlightLog Analyzer plans with 300 ft per nm, and uses your measured gradient during a live climb. |
|
Cruise altitude |
The level altitude the flight plan calls for between TOC and TOD. |
|
PEAK |
On a route too short to reach the planned cruise altitude, the highest point where the climb and the 3° descent meet. |
|
Safe altitude |
For one leg: the highest terrain within 4 nm either side, plus 1,000 ft, rounded up to 100 ft. SAFE ALT is the highest over the whole route. Terrain only — not obstacles. |
|
Field elevation |
An airport’s height above mean sea level. |
|
MSL |
Mean Sea Level — altitudes measured from sea level. The vertical profiles use MSL. |
|
AGL |
Above Ground Level — height above the terrain directly beneath the aircraft. |
|
Off route (cross-track) |
How far the aircraft is to the side of the planned route, measured straight across to the nearest leg. |
|
SCALE |
The altitude range of a profile strip, bottom to top. It starts just below the terrain or airports, not at sea level. |
|
Service volume |
How far, and up to what height, a VOR is guaranteed to be receivable — set by its class: T (Terminal), L (Low) or H (High). |
|
Saved flight plan |
The flight plan that was loaded in the simulator during a flight, which FlightLog Analyzer saves with the flight’s telemetry. Used by Mission Debrief and by Fly It Again’s The Planned Route. |
|
Track (flown path) |
The path an aircraft actually flew: telemetry when recorded, otherwise the positions in the simulator’s logbook. |
|
Procedure |
A published SID (departure), STAR (arrival) or instrument approach: a fixed sequence of waypoints, often with several transitions — versions for different runways or different entry or exit points. |
|
Navigation database |
FlightLog Analyzer’s built-in data on airports, navaids, fixes and procedures. Its procedures are the current versions, which aren’t necessarily the ones you flew months ago. |
|
Runway transition |
The part of a SID or STAR for one particular runway, named RW plus the runway (RW26L; RW26B covers both parallel runways 26L and 26R). Which ones a procedure publishes tells you which runways it serves. |
|
Enroute transition |
The part of a SID or STAR that links it to the en-route part of the flight, named after the fix where it ends (a SID) or begins (a STAR). A procedure often has several, one for each direction. |
|
IAF |
Initial Approach Fix — where an instrument approach begins. An approach can have several IAF transitions, one for each direction of arrival. |
|
Traffic flow |
The direction a busy airport is using its runways in, set by the wind — for example “east flow” or “west flow” at Atlanta. Many airports publish different SIDs and STARs for each flow. |
If a new version causes problems, you can roll back to a previous one. Visit the Change Log page on FlightLogAnalyzer.com and click the version number of any prior release to download and install it.
If something goes wrong after a Logbook Cleaner or Flight Fixer operation — for example, Flight Simulator starts with an empty logbook — use Edit → Restore FlightLog… and pick a recent restore point.
We're aware of this issue but don't yet have a permanent fix — it appears to be a Leaflet rendering quirk. The workaround: uncheck Satellite Overlay, then check it again. The missing tiles fill in correctly on the second pass.
On some Windows 11 PCs, a FlightLog Analyzer message or window opens but never appears on screen. The program seems to stop responding, yet pressing Esc (which closes the invisible popup) brings it back. This is caused by a Windows display feature called Multiplane Overlay (MPO), not by FlightLog Analyzer: on certain graphics cards and drivers it can leave windows undrawn, and it affects other programs too. Turning MPO off fixes it:
1. Press Windows key + R, type regedit and press Enter (this needs an administrator account).
2. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Dwm.
3. Right-click in the right-hand pane, choose New › DWORD (32-bit) Value, and name it OverlayTestMode.
4. Double-click OverlayTestMode, set its value to 5 and click OK.
5. Restart the computer.
To undo it, delete OverlayTestMode and restart. NVIDIA publishes this same change as an official fix, and a later Windows or graphics driver update may make it unnecessary.
If FlightLog Analyzer starts but the main display is empty, your logbook wasn't at the expected default location. Use File → Logbook Locator for Non-Standard FS Installations.
The Locator asks for a starting directory and drills down from there, checking files one at a time. It can be slow, so pick the deepest known directory you can. For example, starting at
C:\ will check every file on your C: drive — that takes a while. If you know Flight Simulator is somewhere under C:\MyGames\Simulators, start there.
When the search completes, the located logbooks are presented for you to assign to the correct sim version. FlightLog Analyzer will remember the location for next time.
Most startup crashes trace back to corruption in the logbook file caused by a Flight Simulator crash during a flight. We can usually analyze the file and work around the corruption — send us your logbook and we'll dig in.
The simplest way: File → Send Logbook File to Support. You'll be asked a couple of brief questions, and the logbook is sent along with some diagnostic system info.
Open your temp directory (paste
%temp% into the File Explorer address bar). Find the file FlightLogAnalyzer - TraceLog.txt and open it. Look for a line beginning with +++++ — that's the path to your logbook.
Example trace entry:
+++++C:\users\Geno\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\SystemAppData\wgs\...
Steam installation
If you installed Flight Simulator into the default Steam location, the logbook is at: C:\Program Files (x86)\Steam\userdata\<steamuserid>\1250410\remote\kh_logbook
Microsoft Store installation
The logbook is stored under randomly named folders that change after every flight, so a quick search is needed:
1. Open C:\Users\<user>\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\SystemAppData\wgs in File Explorer.
2. This folder should contain exactly two subfolders: one named "t" and one with letters and numbers. If you see additional folders, they're from prior installations and can be ignored (or removed, after backing up).
3. Double-click the correct folder to enter it, then copy the path from the address bar.
4. Open Command Prompt (Win+R → CMD → Enter).
5. At the prompt, type CD followed by a space, then paste the path. Press Enter.
6. Run: findstr /s /m "LZMA" *.*
7. The search lists matching files. If multiple files are returned, the most recently dated one is your active logbook. Zip it (or upload as-is) and send to support.
LNM may auto-record flights of its own.
If Little Navmap is open while you're flying, it automatically creates its own logbook entries. After importing your FlightLog Analyzer export, you may see duplicates. To distinguish them, look at the Travel Real Time, Aircraft Registration, or Simulator columns: FlightLog Analyzer exports leave those fields empty and set Simulator to "Microsoft Flight Simulator 2020", while LNM's automatic entries fill them in and set Simulator to "MSFS".
Three options for avoiding duplicates:
• Disable LNM's automatic logbook (Logbook menu → uncheck Create Logbook Entries).
• Manually delete the auto-recorded entries before importing (sort by Travel Real Time or Aircraft Registration).
• Clear LNM's logbook entirely before doing a full import.
Empty fields in LNM imports.
A few fields aren't present in the MSFS logbook, so they remain empty in the export:
• Departure and Destination airport names
• Travel and Destination Real Time
• Aircraft Registration
• Distance Plan (nm)
Imported flights have no flight plan or aircraft performance.
MSFS doesn't store the flight plan or aircraft performance file in its logbook either. If you saved them from MSFS, you can attach them manually in LNM by right-clicking a logbook entry and choosing Edit Logbook Entry → Attach File.
1. In SimToolKitPro, choose Flight Tools → Import → Bulk Import.
2. A large text box appears, pre-filled with an example row.
3. Open your FlightLog Analyzer export in Notepad. Copy its contents and paste into the SKTP text box.
4. Click Import.
|
Note: A known bug in SKTP suppresses the "success" message if your pasted content ends with a line break. The import still succeeds — you just won't see the confirmation. To get the confirmation, paste so the cursor ends at the last character of the last line, with no trailing newline. |
Check My Logbook in SKTP to see the imported flights.
1. Use the Volanta desktop application, not the web version.
2. In Volanta, go to Settings → Import/Export → Manual.
3. Select the Volanta CSV file you exported from FlightLog Analyzer.
4. Expand the Flights section.
5. Select the flights you want to import.
6. Click Start Import.
Unlike the other export formats, Sky Dolly exports create a separate .gpx file per flight. When exporting, you'll be asked to choose (or create) a target directory; the resulting folder contains one .gpx per flight.
To import into Sky Dolly:
1. In Sky Dolly: File → Flight Import → GPX format.
2. Choose Import Directory to import all flights at once (note: all imported flights will share the same airplane label).
3. Select the directory containing your .gpx files.
4. Pick an Aircraft (it's just a label, doesn't affect recording/replay).
5. Leave Waypoints and Position at their defaults (<wpt> for waypoints, <trk> for position).
6. Leave Default Altitude and Default Speed as-is.
7. Uncheck "Convert Altitude from WGS84 to..."
After import, the flights appear at the end of Sky Dolly's logbook.
|
Note: Flight Simulator's logbook is just that — a logbook, not a full flight recording. Don't expect Sky Dolly playback to perfectly reproduce the flight; the track data in MSFS's logbook will only give a reasonable approximation. |
If you create flights using a third-party planner (PMDG, Maddog, iniBuilds, etc.) rather than the default MSFS planner, this information may be missing from your flights. The reason: third-party planners don't store the flight plan in Flight Simulator's logbook, so there's nothing for FlightLog Analyzer to read.
If an airport’s name is missing or wrong in the main display, give it your own: click its From Name or To Name cell and type the name — see Naming an Airport under Editing Flight Records. Your names are kept in MyAirportNames.txt (Edit > Edit My Airport Names ...), so they survive updates of the built-in airport data.
If it is a real airport that’s missing from the built-in data, please also let us know at Support@FlightLogAnalyzer.com so it can be added for everyone.
The elevation profile shown on the Features page of our website isn't a FlightLog Analyzer feature directly — it's a Google Earth feature you can use on any exported flight. To see it:
1. Select the flight you want to profile.
2. Right-click it and choose Show Elevation Profile from the context menu.
|
Tip: Click and drag across the profile to highlight the corresponding section of the flight on the map above. |
FlightLog Analyzer occasionally shows informational alert popups with a Show Again checkbox. Unchecking it hides that popup permanently — until you reset them. To reset all Show Again selections, use Edit → Reset All "Show Again" Selections.
Questions and suggestions can be sent to Support@FlightLogAnalyzer.com. Your input helps make this software better — we always enjoy hearing from you.
• Your license agreement is for single-user use only.
• It is against the license agreement to perform logbook editing, exporting, or any other FlightLog Analyzer function as a paid service to others.
To register, open the Registration menu, paste your license key into the box (the Paste button does it in one click) and click Register. The window then shows who the key is registered to and whether it’s a Standard or PRO license.

The User Registration window (the license key is blurred here)
License keys now start with FLA2-. If you bought FlightLog Analyzer before version 3.5.5.0, there’s nothing to do: your key switches to its new form by itself the next time FlightLog Analyzer checks in, and this window then shows the new key. Keep a copy of it with your purchase email. Nothing else changes: your key keeps working on your PCs just as it does today.
Retiring an old PC? Unregister this PC takes your license key off it. It asks first and shows you the key, so you can keep a copy for your new PC. The button only works for the key that’s registered on this PC, not one just pasted into the box.
FlightLog Analyzer sends a few anonymous counts about five days of use (the first five days of your free trial and, once you’ve registered, the first five days of each new version), so we can see what people find useful and make it easier to get started: whether a logbook was found and loaded, roughly how many flights it holds (as a range, never the exact number), which windows you opened, and how long you used the program. No flight data, logbook contents, file names or personal details are sent. To stop it at any time, untick Help > Send Anonymous Usage Counts.
Thank you for supporting FlightLog Analyzer! We're grateful to be a part of your flying — helping you manage and analyze your logbook with ease and precision. The app was built with pilots and aviation enthusiasts in mind, and your feedback is what keeps it improving.
Whether you're a professional pilot or someone who simply loves aviation, we hope FlightLog Analyzer earns a permanent spot in your cockpit or on your desk.
Please don't hesitate to reach out — Support@FlightLogAnalyzer.com.
Safe travels, and thank you for flying with us.
— 2 Guys with a Keyboard
The screens below walk through every step of loading a FlightLog Analyzer-exported .PLN file into MSFS 2024, from the pre-flight screen all the way to sending the route to the aircraft.

The pre-flight screen, with the EFB button highlighted
From MSFS 2024's pre-flight screen (the one showing your route distance and the Start flight button), press TAB — or click the EFB button directly — to open the Electronic Flight Bag.

The EFB's home screen
On the EFB's home screen, click Flight Planner.

The Flight Planner's left-hand sidebar
In the Flight Planner, click the Route icon in the left-hand sidebar (the second icon down).

The Route page's toolbar
At the top of the Route page, click the folder icon next to Import.

The Import menu
Choose Load PLN File from the menu that appears — not Load from Web, Enter Route String, or Request from Avionics.

The Load / Save Flight Plan Files screen
Choose Load from this PC. In the Windows file browser that opens, the quickest way is to press Ctrl+V in the File name box and then Enter: when FlightLog Analyzer exports a plan it puts the file’s full path on the clipboard. Or browse to it yourself — exports go to Documents\FlightLog Analyzer\Flight Plans unless you choose another folder.

The imported route, shown on the Route page and the map
MSFS loads every waypoint from the file and draws the route on the map. Once you've confirmed it looks right, click SEND at the top of the Route page.

The Send menu
Choose Send to ATC and Avionics to load the route into both the aircraft's own flight computer and ATC. Your flight plan is now ready to fly.