Exactly how it originally did!
1 Like
I had a weird experience yesterday. After I landed I let the AI taxi back to the gate. While I was not paying attention the co-pilot decided to end us all by taxiing into the terminal building ending the flight.
But the flight was logged. Itās perplexing.
2 Likes
Today flight, 1 h stop logging after 14 minutes as āvicinityā. Perhaps I overstressed aircraft but I didnĀ“t crash.
While the flights not logging is annoying, to me losing another top 50 landing challenge score because it wasnāt logged is more of an issue. Several hours down the drain again and again. I hate my time being wasted by a product I paid full price for. Please fix this. It worked again shortly after the last patch and now it is broken again. I have made no changes nor used the Developer mode between when it works and when it does not.
My Logbook recorded several Cessna landing lessons, two days ago (1.9.5).
For other planes, after landing turning off the engines triggers the logbook immediately. So try that and good luck!
1 Like
Itās strange, Iāve not seen a single video by anyone yet demonstrating this problem. What I was hoping to see was an end to end flight of someone with the issue, showing exactly what they do, and when, which leads to this problem. Text is one thing, but I was hoping to actually see.
Even a short hop/route that someone has had issues with that could be replicated by others, although I know the location makes no difference it at least gives something others could stick to for testing purposes.
But not one. A ten minute flight would suffice.
This issue needs to get more attention from the developers. I just completed about two hours of flight, with a takeoff and IFR landing at KHOU. The logbook entry for the flight looks like this:
No, landing, not takeoff, and not time allotted to the flight. Some of my flights allocate some of the time I spent flying, but not all. Some log a takeoff, but not a landing, and some log a landing without a takeoff.
The inaccurate log entries make the logbook really useless at this point. Iād rather it not even exist if it continues to behave in this way.
I hope others will upvote this thread so the developers will look at it more closely.
Are you sure that wasnāt a subsequent flight, where you spawning in to test logging? Or maybe the flight before that?
Iām sure. Itās the last entry and only recent entry for the TBM 930.
Iāve put up a couple of logbook entries showing incomplete flights so would be worth trying one of those. Added them again below. Just pick one with no landing. Top one is nice and short.
As for a video on holding off flying until they fix this. Thereās enough people having the same error to show that itās occurring.
Thanks for those, although since they are logging for you. There appear to be two issues, where some have their flights not logged at all, and others find that certain takeoffs/landings donāt seem to count. Itās my experience that ATC interaction is key to both being logged. Just taking off almost certainly wonāt get logged, but requesting landing clearance via ATC will cause the landing to be logged.
So I may try just that, after the patch is released today. What Iāll try is a flight from LATI to LW75, both of which are in your logs. Instead of seeing what I end up with, I will try in effect to create a log. I will take off from LATI without requesting clearance, and land at LW75 where I will request landing clearance. What I would hope to see is no take-off logged, but one landing logged.
Itās only a 84nm flight, so I might also perform the reverse, logging a takeoff from LW75, but just landing without clearance at LATI.
I hope the scenery is nice there! 
The issue I get is the landings not logging. I follow ATC, request landing, parking, shutdown etc each time (might as well do it properly).
The flight you mention was LATI to LWSK (where I landed) but it only partly logged to LW75. As for the scenery I have no idea as I did the whole flight in a thunderstorm due to another bug! Let me know if you see anything nice. Happy flying!
1 Like
Okay, as expected, ignoring ATC on take-off, but requesting a landing at the untowered airport, taxiing just off the runway, then reporting clear, and shutting down logged no take-off, but one landing.
No suprises there. Now to run the reverse course. Iāll attempt to log a take-off but no landing. The idea would be to land at LATI without clearance, then contact ground after taxiing off the runway, and get the opposite to log correctly.
Before the patch,the logbook worked without doing anythingā¦pressing escape to the main menu the flight was logged
Okay, that was interesting. LW75 has no parking, so you have to start on the runway. I announced take-off straight out, and headed back to LATI.
I landed at LATI on runway 35 but did not contact ATC. When on the ground, and still on the runway, I noticed the option to contact ground had appeared, so I requested taxi to parking.
Oddly, both the take-off and the landing were logged correctly.
True. and that is how it should work.
Yeah, I remember that. You could just hit Esc, and quit to menu, and it would still log. I donāt remember about the landing/takeoff detection though.
To be fair, using ATC is not hard, and does work as my logs show, but you shouldnāt have to.
1 Like
Thanks for flying it. Itās certainly odd. As the patch has been delayed I might see if I can get in a few test runs between LATI and LWSK (and vice versa).
I find it curious that it took LW75 to be my destination rather than LWSK. Iām wondering if waypoints might be an issue. Only one way to find out.
Also what are you using to plot your flight like that?
1 Like
I fully agree
ATC and controlled airports are not working for me in terms of flight logging.
Sometimes it will log a flight and sometimes it wonāt. It can be the same flight in the same plane, and it still is hit or miss.