I’ve done it that way and still no joy getting it to log. Shouldn’t be this hard to get the flight to register.
Was much easier in previous patches/beta.
…and yet, according to the roadmap, they are prioritizing removing “Press Any Key to Start” in the next patch!
Who says they are prioritizing that above fixing the logbook problem? The skipping of the keypress is hardly time consuming for them..
I never use the objectives window, and in fact have that option turned off.
The window I left open at untowered airports was the ATC window. When you taxi off the runway, the ATC option to report being clear of the runway appears. That’s the way I know I can get my flight to log. I want to know straight away, as if you taxi far enough away you will be logged as being in the “vicinity” of the airstrip.
I have a work around that shows the sad state of affairs that this is in.
I too have the logbook problem. A few patches ago it quit logging properly. Before it was fine. Now it only logs if it sees an official end to a flight. So I follow everything to the letter, park, and shut down and hope that I get the end of flight pop-up.
Today after a 1 hour flight, I didn’t get the pop-up. I sighed knowing it wasn’t going to go in my log.
Then I saw the rather large hangar I was parked by…
I fired up the plane and purposely crashed into the hangar. Since it was an official end to the flight, the entire flight was logged. 
How sad is it that I have to actually crash the plane on purpose to get the flight to go into the log?
1 Like
Ever since I enabled the AI to handle ATC, all my flights are being properly logged, even when landing at small airfields.
I dislike having the radios on and hearing the moronic ATC, but for now this seems a reasonable workaround.
1 Like
I’ve had success at uncontrolled airports by parking on the ramp, chopping the fuel off, then shutting down the Garmin power switches. As I go to turn off the battery switch I get the close out pop up, and it Consistently records My landings. But your mileage may vary.
1 Like
Would anyone having this problem care to point to a video demonstrating it? I’ve seen plenty of text, but not a video. I for one would like to see what is being done to cause this bug. I’m quite happy to reciprocate.
For me after version 1.8.3.0 the “My Logbook” has been inconsistent. It worked flawlessly prior to 1.8.3.0 Either the flight time is truncated. 1.5hrs when the flight actually lasted 2.5hrs to not even logging any hrs/flight at all. This is a ridiculous bug to have and poor quality control if basic game logging is something they managed to break after a patch.
The logbook is clearly broken, How about a word from the developer on a FIX?
I need to do more test runs, but I got my first counted landing at an un-towered airport.
I kept the objectives window opened the entire flight (quick flight ifr from krdu to ktta, with rdu vor as only waypoint). Performed ILS landing on rw 3.
I kept comms on the approach channel vs the traffic channel, since I already know nothing is broadcast on traffic. However, nothing was different on approach channel.
Once I touched down, I normally would get off the runway and onto a taxiway immediately to park. However, this time I noticed the objective said to slow down to 15kts and leave runway. So I applied brakes until I slowed down enough and exited runway at next taxiway entrance. Once I left the runway, the objective changed to end of flight. This was without declaring clear of runway. I shutdown engines and got the pop-up and a landing logged. I did not go to the normal parking area, I shutdown just past the hold line.
Will try a few more runs tomorrow after work.
1 Like
Hello everyone,
Please make sure that the DEV Mode is off!
If not, your logbook will not save your flight sessions’ information.
1 Like
the dev mode is off…The logbook is broken
1 Like
I’d still like to see a video of this in action, so I can replicate. I fly GA, so please try to keep it under 100 miles if you don’t mind! 
I’ll then fly between the same airports, record the whole thing, and see if I get the same result.
Just finished a VABB-EGLL flight. Logbook is bugged man 
Having Dev mode off doesn’t help for many. It’s broken and has been for the last 3 patches.
2 Likes
I am seeing all my Log Book problems with Dev-Mode being “OFF”.
However … I once (in 1.8.x) activated dev mode to check the rendering performance. Not sure if that is leaving “traces” somewhere.
But the Log problems only affect ca. 50% of my trips … and there is no clear pattern (so far) to be seen.
- It is not limited to the first flight during a process run
- It is not limited to short or long flights
- It does not matter if I “ESC” after landing and halting on the runway
- It does not matter if I taxi close to the airport building
All are affected by the same sporadic pattern.
For now I just flight and land controlled airports, before landing, I open the ATC window and as soon as I get off the runway contact the ground by my self if my co-pilot is not doing his job and go to the parking spot assigned to you ONLY not any spot, if you landed a big airport, you might not know where the spot is if you don’t have chart, turn on the taxi ribbon and follow it then do the shut down, don’t go to any spot that taxi ribbon show you without contact the ground, often it changes, this way I got 100% log.
By the way, I flight GA only for now, will test those uncontrolled air field soon
Hi Olie
Please accept that this is a bug and take care that the developers are looking into this issue (so many people are reporting this bug).
Also for me dev mode is OFF. Almost no flight will be logged correctly - I’m not able to recognize a pattern.
Many will not be logged at all. Many will be logged with no landing - even if there was a proper landing (and taxiing to parking procedure) - but stating the arrival with ‘Vicinity’. A correctly logged flight is an exceptional case.
Even during the Beta testing the flights was logged correctly. But now the flight logging is clearly messed up.
Thanks.
Someone over at AVSIM suggested that usage of ATC might trigger logbook entries and if destinations and arrivals are counted. I keep an eye on this since, and while I wouldn’t go so far to confirm this 100%, ATC usage “seems” to support logbook entries as well as destinations/arrivals being counted for me.
No developer mode in use right now, but I had it on twice, I think.
I have those logbook issues already since the previoius patch and made a Zendesk report some time ago.