How do I use the logbook in Prepar3D?

Prepar3D’s built-in logbook records completed simulator sessions, including the aircraft, date, departure, arrival and flight time. Open Logbook or Pilot Records from the main interface, review the entries, and end each flight normally so it is written. Back up the logbook data before resetting, upgrading or reinstalling Prepar3D.

Where is the logbook in Prepar3D?

The Prepar3D logbook is opened from the main or start interface, not from the cockpit’s Navigation Log. Its exact placement and name differ between major releases, so look for Logbook, Flight Log or Pilot Records.

1. Return to the main interface: if no logbook command appears while a scenario is running, save or end the scenario and return to Prepar3D’s start screen.
2. Open the logbook: select the available Logbook, Flight Log or Pilot Records command. The built-in Learning Center can help locate it when a release has rearranged the menus.
3. Select an entry: review its date, aircraft, flight time and recognised departure or arrival airports.
4. Finish flights cleanly: land, park if appropriate, then use Prepar3D’s normal end-scenario command. Do not assume touchdown alone has committed the entry.

Our cross-simulator guide to logbook menus and recorded data explains how the terminology differs between simulators.

What does the Prepar3D logbook record?

The built-in logbook provides a basic flight history rather than a detailed flight-data recording. Depending on the Prepar3D release, expect fields such as the aircraft, date, duration and recognised departure and arrival locations.

An empty or incorrect airport field does not necessarily mean the flight failed to save. Prepar3D may not identify an airport when the scenario begins in the air, the aircraft is moved with slew or repositioning commands, or the flight ends away from the airport reference area.

Do not confuse the logbook with a saved scenario or the Flight Planner’s Navigation Log. A saved scenario preserves the aircraft’s state so it can be resumed; the logbook merely records that a session occurred. Its times should not be treated as a legally valid pilot log because pauses, simulation-rate changes, resets and airport detection can affect the result.

Why is the Prepar3D logbook not recording flights?

Missing entries usually result from an abnormal shutdown, an unwritable user folder, a different Prepar3D profile or version, or damaged logbook data.

1. Run a controlled test: use a default aircraft, start at a known airport, make a short flight to another recognised airport and end the scenario through Prepar3D.
2. Avoid forced shutdowns: closing Prepar3D through Task Manager or losing the application to a crash can prevent the final entry being written. If this happens regularly, follow our Prepar3D crash-diagnosis checklist first.
3. Check the Windows account and simulator version: separate Windows users and major Prepar3D installations can maintain separate records. An older logbook is not always migrated automatically.
4. Check folder access: Windows security controls, a redirected Documents folder or synchronisation conflicts can stop Prepar3D writing to its user files.
5. Test for corruption: close Prepar3D, find the logbook data in the version-specific Prepar3D folder under Windows Documents, and copy it somewhere safe. Rename the original rather than deleting it, then restart Prepar3D so it can create fresh data. If new flights now save, the old logbook was probably damaged.

Do not edit binary logbook data in a text editor. Keep the backup until the replacement has recorded several flights correctly.

Should I use the built-in logbook or an external one?

Use Prepar3D’s logbook for a simple history; choose another method when you need searchable routes, exports, training notes or reliable block and airborne times.

Whichever method you choose, make periodic backups. Prepar3D reinstalls, major-version upgrades and corrupted user files can otherwise erase years of accumulated records.