Are you sure that the 540k file is for the logbook?
Check all the subfolders in wgs.
For me, it had 6000 flights and the last one was on 4 April 2025. After I deleted my logbook file in wgs, a new one started, with no flight in FS2024 logbook.
Now I have ~ 300 flights:
My logbook file is now 588 kB:
So: 601,398 / 298 = ~ 2018 B per flights
When my logbook file was ~16 MB, I had 6000 flights: (I made a copy of that file)
So:16,775,869 / 6000 = 2795 B per flight
For me I have 15 flights since clearing the file and it now stands at 13.5mbso the size of my file is mainly driven by my profile associations I believe (the more I add the bigger the file gets).
The system seems to behave differently in different people… Maybe the system decides what to do, where to save… 
No wonder it is hard for Asobo to fix the problem. 
It has occurred to me that the file I think is “the logbook file” is actually not and is my “control profile” file. I have no other file that is anywhere even approaching 1mb. It may be that ANY file that exceeds 16mb throws a 2047.
Since switching to Spad, I can tell you the size/growth of the logbook/whatever file doesn’t have any connection to control profiles. It seems to grow at several mb per flight for me, and at maybe half that speed with dev mode on when it shouldn’t be logging at all
Yet @RevampedSine732 has 300 flights and the file is only 555kb.
It’s happening to me now whilst trying to do career stuff but I’m on xbox so can’t delete things akin to PC users. So frustrating
Yeah I’m on Xbox, flying the pmdg 737 into anchorage.getting set up for decent enjoying the veiw,boom error 2047…game over!.
Frustrating!!!…..
Same thing happening to me on Xbox X idk is there any way to fix this? Read posts saying even when you clear everything it comes back. And no word from devs….. everything else is great but with this error popping up can’t fly anymore…
Specific Xbox bug report for 2047. Please vote there as well if you’re on Xbox with this error.
I actually thought this was fixed. Did t get a single error for 2 days straight then today bam it’s back every 30mins
This is a joke where are the devs ack?
