LOOK AT THE DATE OF THE LOGBOOK ENTRY
You can quickly identify the date your logbook started misbehaving by looking at the date of the most recent log entry.
EXIT DEVELOPER MODE – DON’T JUST TURN IT OFF
It appears that developer mode – unsurprisingly – may interfere with the logbook triggers. Specifically, if you are messing with CFG file parameters and using developer mode to resync the plane, it may keep the logbook from updating.
Go to the developer mode menu (upper left in flight screen) and select “exit” to exit developer mode. It may be that just turning it off in the options screen still hangs up the logbook logic.
HAVE THE OBJECTIVES WINDOW OPEN
To make sure you meet all the objectives for a flight, keep the objectives window open and complete them all.
USE ATC ASSISTANCE FOR TAXIING TO GATE / PARKING
Departures seem seem to always log correctly since the early December patch – takeoffs and in-air departures. Landings seem to be much more picky, but here’s what has always worked for me:
At controlled airports you don’t have to use ATC for landing, but after you land, exit the runway onto a taxiway. Tune ground, and ask to taxi to the gate or to GA parking. Turn on navigation assistance before you do this. ATC will provide instructions and blue arrows to the parking location. Acknowledge the taxi instructions, then taxi to the indicated space – it turns green when you’re in the right location. Kill the engine and then kill the master battery. You should get the end of flight menu – and I always exit to the main menu instead of continuing the flight.
At uncontrolled airports, you won’t be able to get ATC taxiing instructions, so just kill the engine and then the battery as soon as you get off the runway and stopped on the taxiway.
REFLY THE MOST RECENT LOGBOOK FLIGHT TO “UNHANG” IT
Make sure you’ve exited developer mode, then click on the most recent logbook entry. You’ll see an option to fly that flight again. Re-fly it using the techniques above to end the flight.
HOW TO KNOW IF IT FIXED THE LOGBOOK PROBLEM
If the procedures above fixed the problem, you should see today’s date for the logbook entry. If it didn’t, it will still be the date when it first broke.
A320 / ENGINE WON’T SHUT DOWN BUG
If you are unable to shut down the plane’s engine, then you may not be able to trigger the end of flight logic, or it might not correctly trigger the logbook logic even if you do get the end of flight screens.
Try flying the most recent leg with a different plane whose engines WILL shut down. I think it’s just the landing, taxiing, and shut-down portion that is necessary to make the logbook work again.
Good luck and happy flying!