Recover a missing FS2004 logbook by finding Logbook.BIN, restoring the correct copy and fixing Windows profile, folder or permission problems.
To recover a missing FS2004 logbook, close FS2004, locate Logbook.BIN in your user’s Documents\Flight Simulator Files folder, back up every copy you find, then restore the newest known-good file there. If no backup or recoverable copy exists, FS2004 cannot recreate past entries automatically.
Where is the FS2004 logbook stored?
FS2004 normally stores its logbook at Documents\Flight Simulator Files\Logbook.BIN, called My Documents\Flight Simulator Files on older versions of Windows. It is a user file, not part of the main FS2004 installation directory.
The actual Documents location may have moved to another drive, a redirected OneDrive folder or a different Windows profile. Search all drives and user accounts for Logbook.BIN; Windows filenames are case-insensitive, so logbook.bin is the same file.
How do I restore Logbook.BIN safely?
The safe recovery method preserves every candidate before replacing the active logbook.
- Close FS2004 completely. Confirm that
fs9.exeis no longer running before copying or renaming the file. - Show filename extensions. This prevents accidentally creating a name such as
Logbook.BIN.bin. - Find every copy. Check the active Documents folder, other Windows profiles, old drives, the Recycle Bin and any Windows backup or file-history locations.
- Protect the originals. Copy each candidate into a separate backup folder and retain its original modified date. Do not edit
Logbook.BINin a text editor; it is a binary file. - Identify FS2004’s active folder. It is normally the
Flight Simulator Filesfolder containing your saved flights. If uncertain, save a disposable flight, close FS2004 normally and find where the new flight files appeared. - Swap the file while FS2004 is closed. Rename the existing active file to something such as
Logbook.current-backup.BIN, copy the chosen candidate into the folder and name it exactlyLogbook.BIN. - Check write access. Make sure the restored file is not read-only and that your Windows account can write to the folder.
- Test before discarding anything. Open the logbook, complete a short test flight and exit FS2004 normally. Confirm that the file’s modified time changes and make another backup if it works.
Which Logbook.BIN copy should I use?
Use the most recent copy that opens correctly and still contains the expected entries, not simply the file with the newest timestamp.
| Candidate | What it probably represents | What to do |
|---|---|---|
| Older file containing your flights | A usable backup from before the loss | Restore it, accepting that later entries may be absent |
| Recently created file with no history | A fresh or replacement logbook | Keep it as a backup, but search for an older populated copy |
| File that causes an error or prevents a normal exit | A damaged logbook | Stop using it and try another preserved copy |
| File under another Windows profile | The logbook used when FS2004 ran under that account | Copy it into the active profile while FS2004 is closed |
A common mistake is repeatedly launching FS2004 and overwriting possible evidence before making backups. Reinstalling the simulator will not reconstruct the missing flight history either.
What if no usable logbook file exists?
Without an intact Logbook.BIN or backup, the original FS2004 logbook entries cannot normally be recovered. Saved flights, flight plans and screenshots do not contain enough information to rebuild the built-in logbook automatically.
Check the Recycle Bin and any enabled Windows backup, previous-version or cloud-version history before accepting the loss. Data-recovery tools may sometimes find a deleted file if its disk space has not been overwritten, but recovery is uncertain; preserve the drive rather than installing more software onto it.
Can two FS2004 logbooks be merged?
FS2004 has no built-in facility for merging two Logbook.BIN files or importing individual entries. Choose the most complete working copy and retain the other files separately; attempting to splice binary data manually can corrupt the entire logbook.
How can I stop the FS2004 logbook disappearing again?
The reliable precaution is to copy Logbook.BIN periodically while FS2004 is closed. Also avoid switching Windows accounts unintentionally, confirm that Documents redirection is stable and investigate write permissions if the logbook stops recording new flights.
For an independent record, an FS2004 manager with separate logbook and diagnostic functions can supplement the built-in file. Our collection of FS2004 logging and flight-recording utilities offers other options, although these tools cannot recreate flights that were never recorded or backed up.