How do I use the logbook in Prepar3D?

Prepar3D’s built-in logbook records completed simulator sessions, normally including the date, aircraft, departure, arrival and flight time. Open Logbook or Pilot Records from the start interface, select an entry to inspect it, and end each scenario normally so Prepar3D can write the record. Back up the logbook before upgrades or reinstalls.

Where is the logbook in P3D?

The P3D logbook is normally available from the start interface or main application menus rather than the cockpit’s Navigation Log. The exact label and location vary between Prepar3D releases, so look for Logbook, Flight Log or Pilot Records.

1. Return to the start interface: if no logbook command appears during a live scenario, save the scenario if you intend to resume it, then end it normally.
2. Open the pilot records: select the available Logbook, Flight Log or Pilot Records command. The built-in Learning Center can help when a major release has rearranged the menus.
3. Select an entry: inspect the recorded date, aircraft, duration and any recognised departure or arrival airports.
4. Close future flights normally: use Prepar3D’s end-scenario or exit command. Touching down does not by itself guarantee that the completed entry has been committed to the logbook file.

The Navigation Log is different: it describes a planned route rather than storing past flights. A mistake we see constantly is treating the logbook as a resumable save slot. If you need to continue from the same aircraft state later, follow our guide to saving and reloading Prepar3D scenarios instead.

What does the Prepar3D logbook record?

The Prepar3D logbook provides a basic flight history, not a detailed flight-data recording. Its available fields depend on the release, but commonly include the date, aircraft, flight duration and recognised departure and arrival locations.

A blank or incorrect airport field does not necessarily mean the entry failed. Airport detection can be unreliable when a scenario begins in the air, the aircraft is moved using slew or repositioning controls, or the session ends away from an airport’s recognised area.

Logbook time should not be read as precise block time or airborne time. Pauses, resets, accelerated simulation rates and the point at which the scenario is ended can all make the result differ from the timing rules used by a dedicated logbook app.

Can the P3D logbook replace a real pilot logbook?

No. Prepar3D’s logbook is a simulator activity record and should not be treated as evidence of real-world flying, instruction or legally creditable time. It is useful for tracking virtual flights, aircraft usage and informal training progress.

Where is the Prepar3D Logbook.bin file?

The logbook is normally stored as Logbook.bin inside the version-specific Prepar3D folder in your Windows Documents location. A typical path pattern is %USERPROFILE%\Documents\Prepar3D vX Files\Logbook.bin, where vX represents the installed major version; older releases may use a slightly different folder name.

Documents can be redirected to OneDrive, a network location or another drive, so the path above is only a pattern. Open the actual Documents location shown by File Explorer rather than assuming the file remains under the default user-profile path.

1. Exit Prepar3D: copy the file only after the simulator has closed, so it is not being updated during the backup.
2. Open the correct version folder: if several Prepar3D versions are installed, check the folder matching the version whose entries you have been viewing.
3. Copy Logbook.bin elsewhere: keep the backup on another drive or in a separately backed-up location, not merely beside the original file.
4. Restore cautiously: close Prepar3D, preserve any newly created logbook, then copy the saved file into the active version’s folder. Do not assume that binary logbook files are interchangeable between major versions.

Major Prepar3D releases can keep separate user-data folders when installed side by side. An empty logbook after an upgrade may therefore mean the previous Logbook.bin still exists in the older version’s Documents folder, not that it was erased.

Why is the Prepar3D logbook not recording flights?

Missing P3D logbook entries usually result from an abnormal shutdown, checking the wrong version or Windows account, blocked access to Documents, or a damaged Logbook.bin file.

1. Run a controlled test: use a default aircraft, start at a recognised airport, fly a short circuit or airport-to-airport route without slew, then end the scenario through Prepar3D. Reopen the logbook and check for the new entry.
2. Rule out crashes: Task Manager closures, power loss and application crashes can prevent the final record from being written. If the simulator is unstable, work through our Prepar3D crash-diagnosis checks before repairing the logbook.
3. Check the active account and version: another Windows user and another major Prepar3D installation can each have a separate Documents folder and logbook.
4. Check write access: Windows Controlled Folder Access, synchronisation conflicts and redirected Documents folders can stop Prepar3D updating its user files. Allow the simulator access through the relevant Windows security control rather than permanently disabling protection.
5. Test for corruption: close Prepar3D, back up Logbook.bin, and rename the active copy to something such as Logbook.bin.old. Start Prepar3D and complete another controlled flight so it can create fresh logbook data.

If a new logbook records correctly, the previous file was probably damaged. Our logbook-recovery utility listed for FSX and Prepar3D may help, but compatibility can depend on the file format used by the installed P3D release. Always work on a duplicate and retain the untouched original.

If Prepar3D still cannot create or update the file, the problem is more likely to be the active path, Windows permissions or security software than corruption. Do not edit Logbook.bin in a text editor; it is binary data.

Should I use the built-in logbook or a logbook app?

Use Prepar3D’s built-in logbook for a simple local history; choose a dedicated app or manual training log when you need searchable routes, exports, detailed timing rules or debrief notes.

When comparing logbook apps, check support for your exact P3D major version, how the app defines block and airborne time, whether it exports to a common format, and whether its database can be backed up without the app. Avoid running two automatic recorders with shared imports unless you have checked how they prevent duplicate flights.